Currently, we can't abort the process of node inspection from
ironic api. When a node is not properly setup under inspection
network, admins can only wait it to fail after a specified
timeout value, or by using inspector api, or
``openstack baremetal introspection abort`` command to abort the
introspection process.
Although the inspection state will be synchronized to ironic by
periodic task, it will create a little delay of time. Node state
will be inconsistent between ironic api and inspector api before
next state synchronization. The time defaults to 60 seconds, but
may vary depends to user configuration.
This spec will support ironic handling abort from the inspect wait
state. The inspect wait state is required before this spec can
proceed, which will be addressed by [1].
Reviewed: https:/ /review. openstack. org/482867 /git.openstack. org/cgit/ openstack/ ironic- specs/commit/ ?id=725873a7603 946bd2bf3ba9476 b947f6148fdf2f
Committed: https:/
Submitter: Zuul
Branch: master
commit 725873a7603946b d2bf3ba9476b947 f6148fdf2f
Author: KaiFeng Wang <email address hidden>
Date: Wed Jul 12 17:13:54 2017 +0800
Support baremetal inspection abort operation
Currently, we can't abort the process of node inspection from
ironic api. When a node is not properly setup under inspection
network, admins can only wait it to fail after a specified
timeout value, or by using inspector api, or
``openstack baremetal introspection abort`` command to abort the
introspection process.
Although the inspection state will be synchronized to ironic by
periodic task, it will create a little delay of time. Node state
will be inconsistent between ironic api and inspector api before
next state synchronization. The time defaults to 60 seconds, but
may vary depends to user configuration.
This spec will support ironic handling abort from the inspect wait
state. The inspect wait state is required before this spec can
proceed, which will be addressed by [1].
[1] https:/ /bugs.launchpad .net/ironic/ +bug/1725211
Change-Id: I54775e12ef558f d99c8d6f517e913 48e6f0261c3
Related-bug: #1703089