Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-17164

System cannot boot when usr is a separate file system with latest systemd-219-78.el7_9.8

XMLWordPrintable

    • Yes
    • Critical
    • rhel-sst-cs-plumbers
    • ssg_core_services
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • None
    • All
    • None

      What were you trying to do that didn't work?

      All systems configured with a dedicated /usr cannot boot anymore after updating systemd to systemd-219-78.el7_9.8.

      Root cause is a bad mount unit generation done by systemd-fstab-generator:

      sysroot-sysroot-usr.mount gets generated instead of sysroot-usr.mount.

               Mounting /sysroot/sysroot/usr...
[FAILED] Failed to mount /sysroot/sysroot/usr.
See 'systemctl status sysroot-sysroot-usr.mount' for details.
[DEPEND] Dependency failed for Initrd File Systems.
 :
[    1.781938] systemd[1]: No /sbin/init, trying fallback
[    1.782970] systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory

:/# cat /run/systemd/generator/sysroot-sysroot-usr.mount 
# Automatically generated by systemd-fstab-generator

[Unit]
SourcePath=/sysroot/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
Before=initrd-fs.target

[Mount]
What=/dev/mapper/rhel-usr
# Canonicalized from /sysroot/usr
Where=/sysroot/sysroot/usr
Type=xfs

      This seems to have been introduced by Patch 0853-fstab-generator-Chase-symlinks-where-possible-6293.patch.

      Please provide the package NVR for which bug is seen:

      systemd-219-78.el7_9.8

      How reproducible:

      Always

      Steps to reproduce

      1. Install a system with dedicated /usr
      2. Update it to latest systemd
      3. Reboot

      Expected results

      Boots fine

      Actual results

      Dies

            [RHEL-17164] System cannot boot when usr is a separate file system with latest systemd-219-78.el7_9.8

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (systemd bug fix 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-2023:7468

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (systemd bug fix 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-2023:7468

            Michal Sekletar added a comment -

            dist-git commit with revert,

            https://pkgs.devel.redhat.com/cgit/rpms/systemd/commit/?h=rhel-7.9&id=5ff749ff3be8c695ac6758afb8cea5fdd8368c09

            Michal Sekletar added a comment - dist-git commit with revert, https://pkgs.devel.redhat.com/cgit/rpms/systemd/commit/?h=rhel-7.9&id=5ff749ff3be8c695ac6758afb8cea5fdd8368c09

            Michal Sekletar added a comment -

            Revert of the offending patch,

            https://github.com/redhat-plumbers/systemd-rhel7/pull/149

            Michal Sekletar added a comment - Revert of the offending patch, https://github.com/redhat-plumbers/systemd-rhel7/pull/149

            Michal Sekletar added a comment -

            We have agreed with rhn-support-kwalker and lnykryn@redhat.com that will revert offending patch first so that we can speed up delivery of fixed build before NA holiday weekend 

            Michal Sekletar added a comment - We have agreed with rhn-support-kwalker and lnykryn@redhat.com that will revert offending patch first so that we can speed up delivery of fixed build before NA holiday weekend 

            Stepan Broz added a comment -

            Unfortunately, this issue was not catched during regression testing.

            There is a follow-up upstream patch that is missing in systemd-219-78.el7_9.8 that appears to resolve the issue.

            Verified in the lab.

            Stepan Broz added a comment - Unfortunately, this issue was not catched during regression testing. There is a follow-up upstream patch that is missing in systemd-219-78.el7_9.8 that appears to resolve the issue. Verified in the lab.

            Klaas Demter added a comment -

            I've attached an sosreport of a system with dedicated /usr that booted successfully with systemd-219-78.el7_9.8 to Case 03671470 . During my testing I tried to update all packages seperately (well as far as this was possible). The same machine had a hang when I updated all packages with a simple yum update ( restored from backup before update for testing )

            Klaas Demter added a comment - I've attached an sosreport of a system with dedicated /usr that booted successfully with systemd-219-78.el7_9.8 to Case 03671470 . During my testing I tried to update all packages seperately (well as far as this was possible). The same machine had a hang when I updated all packages with a simple yum update ( restored from backup before update for testing )

              rhn-support-sbroz Stepan Broz
              rhn-support-rmetrich Renaud Métrich
              Stepan Broz Stepan Broz
              Frantisek Sumsal Frantisek Sumsal
              Votes:
              7 Vote for this issue
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: