Bug 2072687

Summary:	Boot fails when using overcloud-full.qcow2 (bios) image
Product:	Red Hat OpenStack	Reporter:	Ketan Mehta <kmehta>
Component:	diskimage-builder	Assignee:	Steve Baker <sbaker>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	17.0 (Wallaby)	CC:	apevec, bshephar, hbrock, jparoly, jslagle, mburns, sbaker, schari, vcandapp
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-common-15.4.1-0.20220509142253.855dcd5.el8ost diskimage-builder-3.20.4-0.20220428174017.555cecb.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-21 12:20:11 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 Ketan Mehta 2022-04-06 18:46:10 UTC

Description of problem:

When using overcloud-full.raw in the default boot mode (bios) , boot is failing as the host enters dracut shell.

From journal logs, the issue seems to be with the missing multipath.conf due to which all the devices are being blacklisted.

Whereas when using the overcloud-full-hardened-uefi.raw image the boot works fine (even in bios mode)

Introspection completes successfully. Issue occurs during node provisioning.

Version-Release number of selected component (if applicable):



How reproducible:
Boot a overcloud node in bios mode with overcloud-full image.

Steps to Reproduce:
1. Upload the images to ironic (/var/lib/ironic/images) overcloud-full.raw, initramfs, vmlinuz
2. Introspect the nodes
3. Provision the nodes
4. Node boot fails due to the mentioned issue.

Actual results:

Node provisioning fails.

Expected results:

Node provisioning should succeed.

Additional info:
I'll mention the puddle id, in a subsequent comment.
Adn the snippet too.

Comment 3 Steve Baker 2022-04-19 21:51:00 UTC

I have replicated this with the image in comment #1 and a locally built overcloud-full booted in bios mode. With the attached fix I no longer get the multpath blacklist error message, but it still doesn't boot on my lab machine, so it is possible that error message is not the root cause.

Comment 4 Steve Baker 2022-04-20 22:31:39 UTC

It looks like the actual issue is the root option is incorrect, so it is attempting to use a root disk uuid which doesn't exist. There is already a fix up for that but I thought it only affected uefi boot:

https://review.opendev.org/c/openstack/tripleo-common/+/826205

I've just proposed a related fix which is required if the kernel is updated during the image build:

https://review.opendev.org/c/openstack/diskimage-builder/+/838792

With these 2 changes I have successfully deployed a locally build overcloud-full

Comment 5 Steve Baker 2022-04-20 22:35:45 UTC

*** Bug 2076577 has been marked as a duplicate of this bug. ***

Comment 6 Steve Baker 2022-04-20 22:37:14 UTC

Targeting to component diskimage-builder, even though part of the fix will be tripleo-common

Comment 12 errata-xmlrpc 2022-09-21 12:20:11 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543