Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1235325

Summary:	"openstack baremetal configure boot" should skip nodes that have maintenance=true
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	python-rdomanager-oscplugin	Assignee:	Marek Aufart <maufart>
Status:	CLOSED ERRATA	QA Contact:	Marius Cornea <mcornea>
Severity:	high	Docs Contact:
Priority:	low
Version:	7.0 (Kilo)	CC:	calfonso, dmacpher, jslagle, mburns, mcornea, rhel-osp-director-maint, sasha
Target Milestone:	y1	Keywords:	Triaged, ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-rdomanager-oscplugin-0.0.9-1.el7ost	Doc Type:	Bug Fix
Doc Text:	The "openstack baremetal configure boot" command attempted to configure nodes in maintenance mode. This caused boot configuration to fail. This fix skips nodes in maintenance mode. Now the boot configuration passes without error.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-08 12:10:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Udi Kalifon 2015-06-24 14:08:06 UTC

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.

Comment 4 Marek Aufart 2015-06-29 12:20:22 UTC

Fix is on review https://review.gerrithub.io/#/c/237999/

Comment 6 Udi Kalifon 2015-09-10 12:38:28 UTC

Verified in python-rdomanager-oscplugin-0.0.10-1.el7ost.noarch

Comment 8 errata-xmlrpc 2015-10-08 12:10:02 UTC

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/RHSA-2015:1862