Bug 1377817 - nova instance_uuid not removed from ironic node during reschedule
Summary: nova instance_uuid not removed from ironic node during reschedule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: All
OS: Linux
high
high
Target Milestone: zstream
: 8.0 (Liberty)
Assignee: Artom Lifshitz
QA Contact: Gabriel Szasz
URL:
Whiteboard:
Depends On: 1372392
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 16:42 UTC by Alexander Chuzhoy
Modified: 2019-09-09 16:18 UTC (History)
19 users (show)

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.
Clone Of: 1372392
Environment:
Last Closed: 2018-03-15 12:35:20 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1596922 0 None None None 2018-02-27 11:45:09 UTC
Red Hat Product Errata RHBA-2018:0529 0 None None None 2018-03-15 12:35:37 UTC

Comment 1 Alexander Chuzhoy 2016-09-20 16:43:29 UTC 
Found the issue on 8 and cloned the BZ.
Comment 2 Alexander Chuzhoy 2016-09-20 16:45:43 UTC 
The workaround is to run:
ironic node-update <node uuid or name > remove instance_uuid
Comment 3 Robert Rati 2016-09-20 16:58:43 UTC 
(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.
Comment 12 errata-xmlrpc 2018-03-15 12:35:20 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.

https://access.redhat.com/errata/RHBA-2018:0529
Note You need to log in before you can comment on or make changes to this bug.