Open Stack

Greetings Paul,

Obviously, deleting and re-enrolling would be an action of last
resort. The only way that I can think you could have gotten the
machines into the provision state of ERROR is if they were somehow
requested to be un-provisioned.

The state machine diagram[0], refers to the provision state verb as
"deleted", but the command line tool command this is undeploy[1].


[0]: https://docs.openstack.org/ironic/latest/_images/states.svg
[1]: https://docs.openstack.org/python-ironicclient/latest/cli/osc/v1/index.html#baremetal-node-undeploy



On Wed, Sep 23, 2020 at 4:58 PM Paul Browne <pfb29 at cam.ac.uk> wrote:
>
> Hello all,
>
> I have a handful of baremetal nodes enrolled in Ironic that use the IPMI hardware type, whose motherboards were recently replaced in a hardware recall by the vendor.
>
> After the replacement, the BMC IPMI-over-LAN feature was accidentally left disabled on the nodes, and future attempts to control them with Ironic has put these nodes into the ERROR provisioning state.
>
> The IPMI-over-LAN feature on the boards has been enabled again as expected, but is there now any easy way to get the BM nodes back out of that ERROR state, without first deleting and re-enrolling them?
>
> --
> *******************
> Paul Browne
> Research Computing Platforms
> University Information Services
> Roger Needham Building
> JJ Thompson Avenue
> University of Cambridge
> Cambridge
> United Kingdom
> E-Mail: pfb29 at cam.ac.uk
> Tel: 0044-1223-746548
> *******************