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.
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 (systemd 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-2022:7727
Description of problem: systemd-fstab-generator debug log message "Found entry what=xxx" has a typo: argument "nofail" and "noauto" are inverted: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 564 log_debug("Found entry what=%s where=%s type=%s makefs=%s nofail=%s noauto=%s", 565 what, where, me->mnt_type, 566 yes_no(makefs), 567 yes_no(noauto), yes_no(nofail)); -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- On line 567, it should be the opposite: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 567 yes_no(nofail), yes_no(noauto)); -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): systemd-239-58.el8.x86_64 How reproducible: Always Steps to Reproduce: 1. Change "/boot" entry in /etc/fstab to add "noauto" 2. Reboot with "systemd.log_level=debug systemd.log_target=kmsg log_buf_len=15M printk.devkmsg=on" on the kernel command line (due to BZ #2059633) 3. Check journal output # journalctl -b | grep -w "Found entry what" | grep "/boot" Actual results: Jun 27 15:23:30 vm-rhel8 systemd-fstab-generator[711]: Found entry what=/dev/disk/by-uuid/17c2c80a-afad-4b64-a31b-55b21ced3740 where=/boot type=xfs makefs=no nofail=yes noauto=no Expected results: Jun 27 15:23:30 vm-rhel8 systemd-fstab-generator[711]: Found entry what=/dev/disk/by-uuid/17c2c80a-afad-4b64-a31b-55b21ced3740 where=/boot type=xfs makefs=no nofail=NO noauto=YES