Bug 2138376

Summary:	NVMe-FC Boot From SAN failing due to missing package
Product:	Red Hat Enterprise Linux 9	Reporter:	Marco Patalano <mpatalan>
Component:	python-blivet	Assignee:	Blivet Maintenance Team <blivet-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	jstodola, mlombard, revers
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-31 10:08:40 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 Marco Patalano 2022-10-28 13:05:09 UTC

Description of problem: I have recently been attempting to configure and test NVMe-FC Boot from SAN. In Beaker, the provisioning is failing. From the logs, I can see that we are installing onto the NVMe-FC namespace:

Configuring storage   
Creating disklabel on /dev/nvme4n1
Creating swap on /dev/nvme4n1p3
Creating xfs on /dev/nvme4n1p4  
Creating xfs on /dev/nvme4n1p2 
Creating efi on /dev/nvme4n1p1

However, the system boots to dracut after the first reboot and I see the following:

[  190.040831] dracut-initqueue[627]: fi" 
[  190.040845] dracut-initqueue[627]: Warning: dracut-initqueue: starting timeout scripts 
[  190.040858] dracut-initqueue[627]: Warning: Could not boot. 
Warning: /dev/disk/by-uuid/d6c85e0d-37e0-4b53-ab92-6ec1dcebf4d4 does not exist 

Below is a sample job:
https://beaker.engineering.redhat.com/jobs/7156224

Digging deeper, we determined that the intrafms image did not include the nvmf module required to Boot from SAN over NVMe-FC. Furthermore, the dracut nvmf module requires the nvme-cli package to be installed. To test this, I added the following to my kickstart:

%packages 
nvme-cli
%end

The installation now succeeds:

https://beaker.engineering.redhat.com/jobs/7176470

Is it possible to detect that we are installing over a NVMe-FC device and mark nvme-cli as a necessary dependency? 


Version-Release number of selected component (if applicable):
anaconda 34.25.1.14-1.el9

How reproducible: Often


Steps to Reproduce:
1. Attempt to provision NVMe-FC BFS using Beaker


Additional info: The installation is successful when performing a manual install with the GUI. In this case, the nvme-cli package is present.

Comment 1 Jan Stodola 2022-10-31 10:08:40 UTC

nvme-cli will be installed when python-blivet supports NVMe-OF devices. This will be done in bug 2123337.
I'm marking this bug as a duplicate.

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