Bug 1627041

Summary:	Cisco UCS 200-M3 blades will not properly boot over the network from IPMI without skipping setting boot device with the IPMI driver
Product:	Red Hat OpenStack	Reporter:	Ramon Acedo <racedoro>
Component:	python-tripleoclient	Assignee:	Dmitry Tantsur <dtantsur>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	akaris, asoni, bfournie, dbecker, dtantsur, hbrock, jraju, jslagle, lmartins, mariel, mburns, mlammon, racedoro, rhel-osp-director-maint, sasha, srevivo, tony.pearce
Target Milestone:	beta	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-10.5.1-0.20180906012844.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, sending an IPMI bootdev command caused some hardware to unexpectedly change the boot device order. This prevented some nodes from booting from the correct NIC or prevented PXE from booting from any location. This release adds a `noop` management interface for the IPMI driver. This interface handles boot commands and prevents bootdev from being used. To prepare for the `noop` interface, you must pre-configure nodes to attempt PXE boot mode from the correct NIC, and then fallback to the local hard drive.	Story Points:	---
Clone Of:	1379010
Clones:	1627043 (view as bug list)		Environment:
Last Closed:	2019-01-11 11:52:59 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:
Bug Depends On:	1379010
Bug Blocks:	1627043

Comment 3 Dmitry Tantsur 2018-09-11 15:03:37 UTC

The code in ironic is already present, so only backporting https://review.openstack.org/#/c/601613/ to tripleoclient for configuration.

Comment 7 Alexander Chuzhoy 2018-10-23 03:14:09 UTC

Environment:
python-tripleoclient-10.6.1-0.20181010222401.8c8f259.el7ost.noarch

Configured management_interface to noop for a subset of nodes:
(undercloud) [stack@undercloud-0 ~]$ for i in `openstack baremetal node list -f value -c Name`; do echo $i; openstack baremetal node show -f value -c management_interface $i; done

compute-0 noop
compute-1 ipmitool
controller-0 noop
controller-1 noop
controller-2 ipmitool


#The boot order was configured accordingly for respective VMs (first network, then disk)
controller-0
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type>
    <boot dev='network'/>
    <boot dev='hd'/>
  </os>
compute-0
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type>
    <boot dev='network'/>
    <boot dev='hd'/>
  </os>
controller-1
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type>
    <boot dev='network'/>
    <boot dev='hd'/>
  </os>
compute-1
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type>
    <boot dev='hd'/>
  </os>
controller-2
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.5.0'>hvm</type>
    <boot dev='hd'/>
  </os>

Successfully deployed overcloud.

Comment 9 Alexander Chuzhoy 2018-10-23 13:02:47 UTC

Verifying based on comment #7

Comment 14 errata-xmlrpc 2019-01-11 11:52:59 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/RHEA-2019:0045