-
Notifications
You must be signed in to change notification settings - Fork 95
Old VM name persists in vmgroup members after photon host VM renaming in vsphere #1357
Comments
@pshahzeb - looks like we need to track rename events in VMChangeListener to update the db. |
Cross-esx multi tenancy related issue and it's a corner case, so we are moving it to 0.17 release. We can pull it back if we have bandwidth since this is a customer issue. |
Cross ESX multi tenancy feature is experimental.So pushing this issue on the back burner for now. @vxav Please take a look at our current design. We would love to hear your feedback! |
Correctness issue - marking as mustfix for Kubecon release. |
@vxav can you please try with the latest (0.17 release VIB)? I have tried on my end and couldn't reproduce the reported issue, sharing the steps with you that I have performed. Using latest VIB:
Steps performed
|
@vxav I am closing this issue please reopen with steps if you are still running into the issue. |
After renaming a Photon host VM (in vsphere) that is part of a vmgroup, the old name persist in the list of member VMs.
This prevents (at least that's what I was doing) the removal of the vmgroup.
To workaround it I opened vmdkops_config.db with SQLite Browser and removed the vm record, which allowed me to remove the vmgroup.
The text was updated successfully, but these errors were encountered: