Bug 1383627
Summary: | `openstack baremetal import` fails with node locked error on "manage" transition | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> | ||||||
Component: | openstack-tripleo-common | Assignee: | Dmitry Tantsur <dtantsur> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> | ||||||
Severity: | urgent | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 10.0 (Newton) | CC: | athomas, dbecker, dhill, dsneddon, dtantsur, jcoufal, jschluet, mburns, mcornea, mlopes, morazi, racedoro, rbartal, rhel-osp-director-maint, slinaber | ||||||
Target Milestone: | rc | Keywords: | AutomationBlocker, Triaged | ||||||
Target Release: | 10.0 (Newton) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | openstack-tripleo-common-5.3.0-5.el7ost | Doc Type: | Known Issue | ||||||
Doc Text: |
Nodes that are imported using "openstack baremetal import --json instackenv.json" should be powered off prior to attempting import. If the nodes are powered on, Ironic will not attempt to add the nodes or attempt introspection.
As a workaround, power off all overcloud nodes prior to running "openstack baremetal import --json instackenv.json".
As a result, if the nodes are powered off, the import should work successfully.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2016-12-14 16:15:50 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: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Marius Cornea
2016-10-11 09:45:40 UTC
With the latest build I am not able to workaround this issue by powering off the nodes before importing them. Please provide openstack-ironic-conductor logs, so that we know what exactly is locking the nodes. Created attachment 1211249 [details]
ironic-conductor.log
Created attachment 1211253 [details]
ironic-api.log
Adding the ironic-api.log as well.
I run into the same issue when all the nodes were powered off and they were registered as 'enroll'. As a workaround I set them to provision state 'manage': for i in `ironic node-list|egrep -v "UU|\+"|awk '{print $2}'`;do ironic node-set-provision-state $i manage;done Probably playing with the ironic config flags 'node_locked_retry_interval' and 'node_locked_retry_attempts' which default 3 and 1 respectively might help. This does not seem to be strictly related to being powered on or off. *** Bug 1385928 has been marked as a duplicate of this bug. *** I think I know the root cause. At least Marius' problem is because of we try powering off the nodes right after registration and before doing "manage". This is 1. wrong (we haven't validated power credentials yet), 2. causes a node to get locked (for a minute in Marius' case). I'm moving the power off to "provide" workflow. 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://rhn.redhat.com/errata/RHEA-2016-2948.html |