You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Currently we are persisting both VM ID and VM name in the backend database. However, VM name can be changed after the VM was created. If this happens, when user executes Tenant Admin CLI such as "vmdkops_admin tenant ls" or "vmdkops_admin tenant vm ls", the command will return obsolete VM names.
Some possible options to resolve this issue:
Don't persist VM name. Always query VM name at runtime
Still persist VM name. When user executes Tenant CLI queries (i.s. "tenant ls" or "tenant vm ls"), query and return the latest VM name, also update the db if necessary.
The text was updated successfully, but these errors were encountered:
Currently we are persisting both VM ID and VM name in the backend database. However, VM name can be changed after the VM was created. If this happens, when user executes Tenant Admin CLI such as "vmdkops_admin tenant ls" or "vmdkops_admin tenant vm ls", the command will return obsolete VM names.
Some possible options to resolve this issue:
The text was updated successfully, but these errors were encountered: