Description of problem: I had 2 nodes in set with maintenance=true in ironic, due to the fact that their ipmi password in instackenv.json was wrong. They were skipped properly by "openstack baremetal configure boot", but when I ran introspection they were not skipped - and of course introspection failed for these 2 nodes. Version-Release number of selected component (if applicable): python-rdomanager-oscplugin-0.0.10-1.el7ost.noarch openstack-ironic-discoverd-1.1.0-6.el7ost.noarch python-ironicclient-0.5.1-10.el7ost.noarch openstack-ironic-common-2015.1.1-4.el7ost.noarch openstack-ironic-conductor-2015.1.1-4.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Register nodes and put a few in maintenance mode 2. Run the "configure boot" and introspection commands Actual results: The system attempts to introspect the nodes that are in maintenance Expected results: Nodes in maintenance should be skipped by introspection
dmitry, I believe this fix would be in the inspector client?
Hi! Maintenance mode is accepted by ironic-inspector for compatibility reason, this will be removed in Mitaka. The real problem is that 'introspection bulk start' command tries to use this nodes, which seems to be a problem in rdomanager-oscclient and should be fixed there.
Fixed in stable/liberty upstream, not sure what state to assign..
The fix is available now
Verified in: openstack-ironic-common-4.2.2-4.el7ost.noarch python-ironicclient-0.8.1-1.el7ost.noarch
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://rhn.redhat.com/errata/RHEA-2016-0604.html