| Summary: | nova instance_uuid not removed from ironic node during reschedule | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
| Component: | openstack-nova | Assignee: | Artom Lifshitz <alifshit> |
| Status: | CLOSED ERRATA | QA Contact: | Gabriel Szasz <gszasz> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.0 (Liberty) | CC: | alifshit, berrange, ccollett, dasmith, eglynn, jhakimra, jtaleric, kchamart, lmartins, lyarwood, mburns, mwitt, rbartal, rhel-osp-director-maint, sbauza, sferdjao, sgordon, srevivo, vromanso |
| Target Milestone: | zstream | Keywords: | Triaged, ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-nova-12.0.6-23.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if an instance associated with an ironic node was scheduled successfully but failed to boot, the nova ironic driver did not clean up the instance UUID. Consequently, the ironic node would no longer be available for new instances. With this update, the instance UUID on the node is cleaned up when destroying the instance. As a result, the node is able to receive new instances.
|
Story Points: | --- |
| Clone Of: | 1372392 | Environment: | |
| Last Closed: | 2018-03-15 12:35:20 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: | |
| Bug Depends On: | 1372392 | ||
| Bug Blocks: | |||
|
Comment 1
Alexander Chuzhoy
2016-09-20 16:43:29 UTC
The workaround is to run: ironic node-update <node uuid or name > remove instance_uuid (In reply to Alexander Chuzhoy from comment #2) > The workaround is to run: > ironic node-update <node uuid or name > remove instance_uuid That is a workaround, but also doesn't relay the full scope of the issue. During an install with director this issue can happen and afaik it's not feasible to run the workaround command during that time. 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. https://access.redhat.com/errata/RHBA-2018:0529 |