Bug 1680927

Summary:	[OSP13] Ironic on new Dell R740 won't reset boot order to PXE after overcloud delete making subsequent deployments fail
Product:	Red Hat OpenStack	Reporter:	ggrimaux
Component:	openstack-ironic	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	mlammon
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	bfournie, christopher_dearborn, mburns
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 12:17:35 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 ggrimaux 2019-02-25 14:56:52 UTC

Description of problem:
Issue: When deploying overcloud for the first time pxe is used and deployment works. But if you delete overcloud and try deployment again, pxe is not put first and because there is still an OS on the nodes, they boot on it and overcloud deployment never work.

Nodes: Dell PowerEdge R740
iDRAC Firmware version used: 3.21.26.22 (latest available, came out a few days ago)

Nodes were using UEFI but now are Legacy BIOS.
iDrac only is being used. Can't use ipmitool because of security constraints.

Have tried deployment with the following:
openstack baremetal node boot device set --persistent compute-0 pxe

boot_mode:uefi was set on the nodes when using UEFI boot mode.

Version-Release number of selected component (if applicable):
openstack-ironic-api-10.1.6-4.el7ost.noarch Mon Feb 18 22:39:43 2019
openstack-ironic-common-10.1.6-4.el7ost.noarch Mon Feb 18 22:39:39 2019
openstack-ironic-conductor-10.1.6-4.el7ost.noarch Mon Feb 18 22:39:48 2019
openstack-ironic-inspector-7.2.1-5.el7ost.noarch Mon Feb 18 22:40:02 2019
openstack-ironic-staging-drivers-0.9.1-1.el7ost.noarch Mon Feb 18 22:39:56 2019

How reproducible:

Steps to Reproduce:
1. Delete overcloud
2. Try deployment again
3. Deployment doesn't work because nodes never boot on PXE.

Actual results:
Subsequent deployment of the overcloud fails because ironic is not able to boot on PXE (boots on disks instead).

Expected results:
Ironic should be able to set boot order to pxe when doing subsequent deployment of the overcloud.

Additional info:

Comment 3 Bob Fournier 2019-03-13 12:17:35 UTC


*** This bug has been marked as a duplicate of bug 1680659 ***