yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #29019
[Bug 1427944] [NEW] instance.host not cleared after reschedule
Public bug reported:
For example, take this scenario:
1. Assume an environment with a single host… call it host-1
2. Deploy a VM, but force an exception in the spawn path somewhere to simulate some "hypervisor error”
3. The scheduler correctly attempts to reschedule the VM, and ultimately ends up (correctly) with a NoValidHost error because there was only 1 host
4. However, the instance.host (e.g., [nova show <vm>]) is still showing ‘host-1’
After discussion on the mailing list and IRC, we decided this should be
considered a bug since the instance is no longer tied to the host since
it blew up in spawn and tried to reschedule. As such, we should clear
it out when the claim is aborted.
** Affects: nova
Importance: Undecided
Assignee: Joe Cropper (jwcroppe)
Status: New
** Changed in: nova
Assignee: (unassigned) => Joe Cropper (jwcroppe)
--
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/1427944
Title:
instance.host not cleared after reschedule
Status in OpenStack Compute (Nova):
New
Bug description:
For example, take this scenario:
1. Assume an environment with a single host… call it host-1
2. Deploy a VM, but force an exception in the spawn path somewhere to simulate some "hypervisor error”
3. The scheduler correctly attempts to reschedule the VM, and ultimately ends up (correctly) with a NoValidHost error because there was only 1 host
4. However, the instance.host (e.g., [nova show <vm>]) is still showing ‘host-1’
After discussion on the mailing list and IRC, we decided this should
be considered a bug since the instance is no longer tied to the host
since it blew up in spawn and tried to reschedule. As such, we should
clear it out when the claim is aborted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1427944/+subscriptions
Follow ups
References