Public bug reported:
Description
============
The "mo-ref" in VMware is not guaranteed to be stable. It can change after a
recovery or simply un-registering and re-registering a vm. So making it stable
is often necessary for the vcenter to be able to manage vms which were "lost"
somehow.
Possible scenario is, when VMs reside on a ESXi host, which was down, and the
ESXi host comes back, but has lost the vm. For the Stable VM refs, we need to
restart the agent to clear out the cache. More problematic is the volume-ref as
there is no fallback to the instance-uuid and we need to modify the db to
reflect the new mo-ref.
Affected versions
=================
vsphere (all), openstack (all).
Steps to reproduce:
===================
For the VM:
1. Create an Instance
2. Stop the instance
3. Unregister the VM in vsphere
4. Register the VM in vsphere
5. Start the instance in openstack
6. An exception is raised
For the volume:
1. Create an instance with vmdk-volume attached
2. Unregister shadow-vm in vcenter
3. Register shadow-vm in vcenter
4. Detach the volume
5. An exception is raised
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1962771
Title:
Implement stable MORef for VMware
Status in OpenStack Compute (nova):
New
Bug description:
Description
============
The "mo-ref" in VMware is not guaranteed to be stable. It can change after a
recovery or simply un-registering and re-registering a vm. So making it stable
is often necessary for the vcenter to be able to manage vms which were "lost"
somehow.
Possible scenario is, when VMs reside on a ESXi host, which was down, and the
ESXi host comes back, but has lost the vm. For the Stable VM refs, we need to
restart the agent to clear out the cache. More problematic is the volume-ref as
there is no fallback to the instance-uuid and we need to modify the db to
reflect the new mo-ref.
Affected versions
=================
vsphere (all), openstack (all).
Steps to reproduce:
===================
For the VM:
1. Create an Instance
2. Stop the instance
3. Unregister the VM in vsphere
4. Register the VM in vsphere
5. Start the instance in openstack
6. An exception is raised
For the volume:
1. Create an instance with vmdk-volume attached
2. Unregister shadow-vm in vcenter
3. Register shadow-vm in vcenter
4. Detach the volume
5. An exception is raised
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1962771/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
