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 1975707 - dracut-cmdline complains with "line 136: /sys/class/fc/fc_udev_device/nvme_discovery: No such file or directory"
Summary: dracut-cmdline complains with "line 136: /sys/class/fc/fc_udev_device/nvme_di...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dracut
Version: 8.4
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-24 09:08 UTC by Renaud Métrich
Modified: 2021-11-10 08:00 UTC (History)
4 users (show)

Fixed In Version: dracut-049-151.git20210719.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:38:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dracutdevs/dracut/commit/0e2ef80993858992f6219b5162289568937a1fac 0 None None None 2021-06-25 07:13:37 UTC
Red Hat Product Errata RHBA-2021:4394 0 None None None 2021-11-09 19:39:06 UTC

Description Renaud Métrich 2021-06-24 09:08:33 UTC
Description of problem:

When having nvme-cli package installed, the initramfs will embed /usr/lib/dracut/modules.d/95nvmf/parse-nvmf-boot-connections.sh.
This produces the following message:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
[    2.952090] dracut-cmdline[319]: //lib/dracut/hooks/cmdline/99-parse-nvmf-boot-connections.sh: line 136: /sys/class/fc/fc_udev_device/nvme_discovery: No such file or directory
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

It's due to a missing carriage return in the script /usr/lib/dracut/modules.d/95nvmf/parse-nvmf-boot-connections.sh on line 136:

Original:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
132     if [ "$trtype" = "tcp" ] ; then
133         /sbin/initqueue --settled --onetime --unique /usr/sbin/nvme connect-all -t tcp -a $traddr -s $trsvcid
134         > /tmp/net.$ifname.did-setup
135     else
136         /sbin/initqueue --finished --unique --name nvme-fc-autoconnect echo 1 > /sys/class/fc/fc_udev_device/nvme_    discovery
137     fi
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Modified:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
132     if [ "$trtype" = "tcp" ] ; then
133         /sbin/initqueue --settled --onetime --unique /usr/sbin/nvme connect-all -t tcp -a $traddr -s $trsvcid
134         > /tmp/net.$ifname.did-setup
135     else
136         /sbin/initqueue --finished --unique --name nvme-fc-autoconnect
137         echo 1 > /sys/class/fc/fc_udev_device/nvme_discovery
138     fi
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Additionally it's very possible that /sys/class/fc/fc_udev_device/nvme_discovery doesn't exist in some cases, hence a 2>/dev/null is welcome here.

Since it's unclear to me whether the missing "echo 1" may prevent booting with NVME-FC, I'm creating the BZ with Sev 2.
Please adjust if it's just cosmetic.


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

dracut-049-135.git20210121.el8.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install nvme-cli and rebuild the initramfs (I did this as a generic initramfs, don't know if that makes a diff)

Comment 1 David Tardon 2021-06-25 07:13:07 UTC
(In reply to Renaud Métrich from comment #0)
> Description of problem:
> 
> When having nvme-cli package installed, the initramfs will embed
> /usr/lib/dracut/modules.d/95nvmf/parse-nvmf-boot-connections.sh.
> This produces the following message:
> -------- 8< ---------------- 8< ---------------- 8< ---------------- 8<
> --------
> [    2.952090] dracut-cmdline[319]:
> //lib/dracut/hooks/cmdline/99-parse-nvmf-boot-connections.sh: line 136:
> /sys/class/fc/fc_udev_device/nvme_discovery: No such file or directory
> -------- 8< ---------------- 8< ---------------- 8< ---------------- 8<
> --------
> 
> It's due to a missing carriage return in the script
> /usr/lib/dracut/modules.d/95nvmf/parse-nvmf-boot-connections.sh on line 136:

No, the "echo 1 > ..." is supposed to be an argument for /sbin/iniqueue . https://github.com/dracutdevs/dracut/commit/0e2ef80993858992f6219b5162289568937a1fac fixes this.

Comment 6 Petr Matyáš 2021-08-16 12:08:53 UTC
Verified on dracut-049-188.git20210802.el8.x86_64

Comment 8 errata-xmlrpc 2021-11-09 19:38:41 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 (dracut bug fix and enhancement update), 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/RHBA-2021:4394


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