Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080621

Summary:	VMware: instance names can be edited, breaks nova-driver lookup
Product:	Red Hat OpenStack	Reporter:	Stephen Gordon <sgordon>
Component:	openstack-nova	Assignee:	Matthew Booth <mbooth>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Henner <jhenner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0 (RHEL 7)	CC:	mbooth, ndipanov, sclewis, slong, vpopovic, yeylon
Target Milestone:	rc
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-2014.1-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, instance names could be edited by vCenter administrators, and badly edited names could break the Compute administration of VMs. With this update, a vSphere metadata value is now used for the VM name (which is not easily edited). This makes Compute lookups far more robust.	Story Points:	---
Clone Of:
Clones:	1086815 (view as bug list)		Environment:
Last Closed:	2014-07-08 15:28:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1055536, 1086815

Description Stephen Gordon 2014-03-25 19:36:40 UTC

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.

Comment 1 Matthew Booth 2014-04-10 15:16:37 UTC

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/

Comment 5 Vladan Popovic 2014-05-28 09:13:38 UTC

Matthew, feel free to add me in the downstream review on all of the patches that you backported.

Comment 6 Jaroslav Henner 2014-06-17 13:39:43 UTC

# nova boot --image rhel-7.0 --flavor m1.tiny bar
# nova stop bar

change the name in the vsphere

# nova start bar

machine started in the vsphere


PASS

Comment 9 Summer Long 2014-06-30 03:56:06 UTC

Matthew, because we're getting to the deadline, I've put in a doc-text suggestion. Could you tech review and get back to me? thanks, Summer

Comment 10 Summer Long 2014-07-02 00:00:08 UTC

No review, so going ahead and moving to + so that it shows up in the notes.

Comment 12 errata-xmlrpc 2014-07-08 15:28:31 UTC

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/RHEA-2014-0853.html