instance.host not cleared after reschedule
Bug #1427944 reported by
Joe Cropper
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Joe Cropper |
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.
Changed in nova: | |
assignee: | nobody → Joe Cropper (jwcroppe) |
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: compute |
Changed in nova: | |
assignee: | Joe Cropper (jwcroppe) → nobody |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | nobody → Joe Cropper (jwcroppe) |
status: | Confirmed → In Progress |
Changed in nova: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | liberty-3 → 12.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/161069
Review: https:/