RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2138376 - NVMe-FC Boot From SAN failing due to missing package
Summary: NVMe-FC Boot From SAN failing due to missing package
Keywords:
Status: CLOSED DUPLICATE of bug 2123337
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: python-blivet
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Blivet Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-28 13:05 UTC by Marco Patalano
Modified: 2022-10-31 10:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-31 10:08:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-137884 0 None None None 2022-10-31 10:16:36 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.