Power off new nodes when making them available, not right after enrolling
Doing it for newly enrolled nodes that didn't go through "manage" action
is wrong, because we only validate power credentials during this action.
Also, this power off request can lock nodes for substantial time, causing
the following "manage" workflow to fail with "node locked" error.
Actually, both ironic and ironic-inspector can safely handle nodes that are
powered on. However, this may be confusing for users looking at node list.
This patch moves powering off to the "provide" workflow with proper wait
and error handling.
Reviewed: https:/ /review. openstack. org/392148 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=fee42cebe27 68bf34101bcd5eb ae5deaebd92e68
Committed: https:/
Submitter: Jenkins
Branch: master
commit fee42cebe2768bf 34101bcd5ebae5d eaebd92e68
Author: Dmitry Tantsur <email address hidden>
Date: Tue Nov 1 14:01:04 2016 +0100
Power off new nodes when making them available, not right after enrolling
Doing it for newly enrolled nodes that didn't go through "manage" action
is wrong, because we only validate power credentials during this action.
Also, this power off request can lock nodes for substantial time, causing
the following "manage" workflow to fail with "node locked" error.
Actually, both ironic and ironic-inspector can safely handle nodes that are
powered on. However, this may be confusing for users looking at node list.
This patch moves powering off to the "provide" workflow with proper wait
and error handling.
Change-Id: Ie2e5baa10adf67 148d335d6127ff1 dfe45e91968
Closes-Bug: #1638281