openstack overcloud node clean --all-manageable should have a flag "--provide" to switch the nodes to available after cleaning. Environment: puppet-ironic-13.3.1-0.20180831191239.61387eb.el7ost.noarch python2-ironicclient-2.5.0-0.20180810135843.fb94fb8.el7ost.noarch python2-ironic-inspector-client-3.3.0-0.20180810080932.53bf4e8.el7ost.noarch instack-undercloud-9.3.1-0.20180831000258.e464799.el7ost.noarch python2-ironic-tests-tempest-1.2.1-0.20180822120435.a0a36fe.el7ost.noarch python-openstackclient-lang-3.16.0-0.20180809175603.f77ca68.el7ost.noarch python2-openstackclient-3.16.0-0.20180809175603.f77ca68.el7ost.noarch 'openstack overcloud node clean --all-manageable' doesn't have the option to switch all nodes to available. This forces the user to do that explicitly. The introspection command has it: 'openstack overcloud node introspect --all-manageable --provide' And the cleaning command should have it too.
Valid feature request (but please do not file tripleo items against openstack-ironic). Note, however, that it should also work with specifying nodes without --all-manageable.
Verified: Environment: python3-ironic-inspector-client-3.5.0-0.20190313131319.9bb1150.el8ost.noarch openstack-ironic-common-12.1.2-0.20190615000404.c3cbdb5.el8ost.noarch openstack-ironic-staging-drivers-0.11.1-0.20190420132245.b7c6755.el8ost.noarch python3-ironicclient-2.7.2-0.20190529060404.266a700.el8ost.noarch python3-ironic-lib-2.16.3-0.20190607070401.eca4ac9.el8ost.noarch puppet-ironic-14.4.1-0.20190423121513.cd9417e.el8ost.noarch openstack-ironic-conductor-12.1.2-0.20190615000404.c3cbdb5.el8ost.noarch + openstack overcloud node clean --all-manageable --provide Waiting for messages on queue 'tripleo' with no timeout. Waiting for messages on queue 'tripleo' with no timeout. Cleaned 8 node(s) 8 node(s) successfully moved to the "available" state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:2811