Description of problem:
I have 2 bare metal nodes whose power state is "None" due to an ipmi bug related to my hardware (see bug 1235255 for details on that). I wanted to proceed with my other 5 nodes so I put the 2 problematic nodes in maintenance and ran the command "openstack baremetal configure boot":

~]$ openstack baremetal configure boot
/usr/lib/python2.7/site-packages/novaclient/v1_1/__init__.py:30: UserWarning: Module novaclient.v1_1 is deprecated (taken as a basis for novaclient.v2). The preferable way to get client class or object you can find in novaclient.client module.
  warnings.warn("Module novaclient.v1_1 is deprecated (taken as a basis for "
WARNING: rdomanager_oscplugin.v1.baremetal.ConfigureBaremetalBoot Node 2a4d7a55-f186-42fa-a84f-3a4ef24fc5cc power state is in transition. Waiting up to 120 seconds for it to complete.
ERROR: openstack Timed out waiting for node 2a4d7a55-f186-42fa-a84f-3a4ef24fc5cc power state.


From the output I got above, it looks like the unified cli is still trying to work with the nodes whose power state can't be set. Those nodes are in maintenance so I expected them to be skipped.


Version-Release number of selected component (if applicable):
python-rdomanager-oscplugin-0.0.8-4.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Put a few nodes in maintenance (you can also misconfigure them, like provide the wrong password to ipmi, to simulate the problem I'm having with my hardware).
2. Run "openstack baremetal configure boot".


Actual results:
The command ignores maintenance flags and fails on the misconfigured/broken hardware


Expected results:
It should be possible for the user to mark failed hardware as "maintenance" and not get stuck with the entire stack just because of 1 issue somewhere.