Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Please enable nvmefc-boot-connections.service in /usr/lib/systemd/system-preset/90-default.preset
# nvme auto connect
enable nvmefc-boot-connections.service
The reason for this change is to allow NVME-FC devices to be available upon
booting (see bug 1801432 for reference).
Hi,
This is currently blocking NVMe/FC autoconnect feature during bootup. So is this on track for a fix in RHEL 8.2 itself? Please confirm. Thanks.
-Martin
Hi Martin,
(In reply to Martin George from comment #8)
> Any updates on this? Is this making it to RHEL 8.2?
All the bugzilla flags are set for inclusion in RHEL8.2,
so it should make RHEL8.2. Thanks.
(In reply to David Milburn from comment #9)
> Hi Martin,
>
> All the bugzilla flags are set for inclusion in RHEL8.2,
> so it should make RHEL8.2. Thanks.
Hi David,
I checked RHEL 8.2 snap2, but I still see FC-NVMe auto-connect failing during bootup here. So is this targeted for snap3 then?
Hi Martin,
(In reply to Martin George from comment #13)
> (In reply to David Milburn from comment #9)
> > Hi Martin,
> >
> > All the bugzilla flags are set for inclusion in RHEL8.2,
> > so it should make RHEL8.2. Thanks.
>
> Hi David,
>
> I checked RHEL 8.2 snap2, but I still see FC-NVMe auto-connect failing
> during bootup here. So is this targeted for snap3 then?
Yes, you should be using redhat-release-8.2-0.9.el8 and
nvme-cli-1.9-5.el8, we verified as long as the
nvmefc-boot-connections.service is enabled when you install
nvme-cli, auto-connect should work after reboot. Thanks.