commit 8ed1c2da1d5aa3e645afac6fdbb64c11cb151664
Author: Jay Faulkner <email address hidden>
Date: Thu May 26 17:31:24 2016 -0700
Ironic nodes with instance_uuid are not available
Currently, if a node is in AVAILABLE or NOSTATE (legacy), regardless of
if it has an instance_uuid it is considered able to be scheduled to.
However, it's impossible for a deployment to succeed to an ironic node
with instance_uuid populated. We should not schedule to nodes in this
state.
Change-Id: I41e0c8f1f8a91e11180a6edd72907cf76fe4b235
Closes-bug: 1503453
(cherry picked from commit ffe3093786b137f46646c4cf5fb3ba6b597418a9)
Reviewed: https:/ /review. openstack. org/323196 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=8ed1c2da1d5 aa3e645afac6fdb b64c11cb151664
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 8ed1c2da1d5aa3e 645afac6fdbb64c 11cb151664
Author: Jay Faulkner <email address hidden>
Date: Thu May 26 17:31:24 2016 -0700
Ironic nodes with instance_uuid are not available
Currently, if a node is in AVAILABLE or NOSTATE (legacy), regardless of
if it has an instance_uuid it is considered able to be scheduled to.
However, it's impossible for a deployment to succeed to an ironic node
with instance_uuid populated. We should not schedule to nodes in this
state.
Change-Id: I41e0c8f1f8a91e 11180a6edd72907 cf76fe4b235 46646c4cf5fb3ba 6b597418a9)
Closes-bug: 1503453
(cherry picked from commit ffe3093786b137f