Red Hat Bugzilla – Bug 1086815
VMware: instance names can be edited, breaks nova-driver lookup
Last modified: 2016-04-26 22:29:57 EDT
+++ This bug was initially created as a clone of Bug #1080621 +++ Description of problem: Currently the VMware Nova Driver relies on the VM name in vCenter/ESX to match the UUID in Nova. The name can be easily edited by vCenter administrators and break Nova administration of VMs. A better solution should be found allowing the Nova Compute Driver for vSphere to look up VMs by a less volatile and publicly visible mechanism. EDIT: A fix would make the link between vSphere and Nova more solid and involve using a vSphere metadata value that cannot be easily edited. Currently the UUID is stored as an extra config metadata property inside vSphere (associated with the instance's virtual-machine) and this value is not easy to accidentally change. That would make the link much more robust. --- Additional comment from Matthew Booth on 2014-04-10 11:16:37 EDT --- The change listed is dependent on 2 other changes, which I have also backported: https://review.openstack.org/#/c/55038/ https://review.openstack.org/#/c/60259/ https://review.openstack.org/#/c/59571/
# nova boot --flavor m1.small --image cirros-0.3.1-x86_64-disk.vmdk foo * edit the VM name in the vcenter # nova delete foo this removed the VM from the VCENTER. I also tried creating two VMs, rename one of them in the VCENTER, upgrade nova, restart nova, and delete the VMs in openstack. Both VMs got deleted from the vCenter.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-1084.html