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 1805466 - /usr/lib/systemd/system-preset/90-default.preset include nvme auto connect
Summary: /usr/lib/systemd/system-preset/90-default.preset include nvme auto connect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: redhat-release
Version: 8.2
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.0
Assignee: Leon Kang
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1776957
TreeView+ depends on / blocked
 
Reported: 2020-02-20 20:31 UTC by David Milburn
Modified: 2022-05-02 00:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-16 13:27:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELBLD-2038 0 None None None 2022-05-02 00:26:39 UTC
Red Hat Issue Tracker RHELPLAN-38281 0 None None None 2022-05-02 00:25:42 UTC

Description David Milburn 2020-02-20 20:31:09 UTC
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).

Comment 1 Martin George 2020-02-25 04:13:41 UTC
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

Comment 8 Martin George 2020-03-03 04:45:56 UTC
Any updates on this? Is this making it to RHEL 8.2?

Comment 9 David Milburn 2020-03-03 21:57:23 UTC
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.

Comment 13 Martin George 2020-03-10 15:30:25 UTC
(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?

Comment 14 David Milburn 2020-03-10 15:56:20 UTC
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.

Comment 15 Peter Kotvan 2020-03-12 11:33:12 UTC
Verified on RHEL-8.2.0-Snapshot-3.0 -> RHEL-8.2.0-20200310.0:

#  grep nvmefc-boot-connections.service /usr/lib/systemd/system-preset/90-default.preset
enable nvmefc-boot-connections.service

Comment 16 Leon Kang 2020-07-16 13:27:52 UTC
Closing this as it was fixed some time ago but i never closed the bugzilla


Note You need to log in before you can comment on or make changes to this bug.