Comment 2 for bug 1945503

This is a bit of a red herring that came up during deployment of new baremetal nodes. The nodes were stuck in 'clean wait' and the nodes were heartbeating properly to ironic-conductor, but because the prior 'clean failed' by the ironic service put the nodes into "maintenance=True" mode, they wouldn't clean upon running 'openstack baremetal node provide <uuid>' without first running 'openstack baremetal maintenance unset <uuid>'.

Ultimately, I think this is an upstream bug that "openstack baremetal node provide <uuid>" should clear the maintenance=True state if it were set True automatically by a prior failed clean action.