Uploaded image for project: 'Image Builder'
  1. Image Builder
  2. COMPOSER-2066

edge-simplified-installer build fails in dracut stage missing nss-softokn

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • osbuild-composer
    • None
    • False
    • None
    • False
    • Testable

      This is a bug that occurred with a customer using RPM mirrors for RHEL 9.2 EUS to build an edge-simplified-installer. The dracut stage fails with the following output

      Stage org.osbuild.dracut
      Output:
      /usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:23: Failed to replace specifiers in '/run/log/journal/%m': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:25: Failed to replace specifiers in '/run/log/journal/%m': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:26: Failed to replace specifiers in '/run/log/journal/%m/*.journal*': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:29: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:30: Failed to replace specifiers in '/var/log/journal/%m/system.journal': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:32: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
      /usr/lib/tmpfiles.d/systemd.conf:33: Failed to replace specifiers in '/var/log/journal/%m/system.journal': No such file or directory
      Failed to open file "/sys/fs/selinux/checkreqprot": Read-only file system
      Building initramfs for 5.14.0-284.30.1.el9_2.x86_64
      /usr/bin/dracut: line 1054: /sys/module/firmware_class/parameters/path: No such file or directory
      findmnt: can't read /proc/mounts: No such file or directory
      dracut: Executing: /usr/bin/dracut --no-hostonly --kver 5.14.0-284.30.1.el9_2.x86_64 --force -v --show-modules --no-early-microcode --reproducible --modules "bash systemd fips systemd-initrd modsign nss-softokn i18n convertfs network-manager network ifcfg url-lib drm plymouth crypt dm dmsquash-live kernel-modules kernel-modules-extra kernel-network-modules livenet lvm mdraid qemu qemu-net resume rootfs-block terminfo udev-rules dracut-systemd pollcdrom usrmount base fs-lib img-lib shutdown uefi-lib biosdevname prefixdevname prefixdevname-tools coreos-installer fdo" --install /.buildstamp
      dracut: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
      dracut: dracut module 'nss-softokn' cannot be found or installed.
      Traceback (most recent call last):
        File "/run/osbuild/bin/org.osbuild.dracut", line 207, in <module>
          r = main(args["tree"], args["options"])
        File "/run/osbuild/bin/org.osbuild.dracut", line 195, in main
          subprocess.run(["/usr/sbin/chroot", tree,
        File "/usr/lib64/python3.9/subprocess.py", line 528, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['/usr/sbin/chroot', '/run/osbuild/tree', '/usr/bin/dracut', '--no-hostonly', '--kver', '5.14.0-284.30.1.el9_2.x86_64', '--force', '-v', '--show-modules', '--no-early-microcode', '--reproducible', '--modules', 'bash systemd fips systemd-initrd modsign nss-softokn i18n convertfs network-manager network ifcfg url-lib drm plymouth crypt dm dmsquash-live kernel-modules kernel-modules-extra kernel-network-modules livenet lvm mdraid qemu qemu-net resume rootfs-block terminfo udev-rules dracut-systemd pollcdrom usrmount base fs-lib img-lib shutdown uefi-lib biosdevname prefixdevname prefixdevname-tools coreos-installer fdo', '--install', '/.buildstamp']' returned non-zero exit status 1.
      

      A look at the customer's manifest (not linked) revealed that the nss-softokn package was not included in the package set for the installer. The package is usually pulled in as an indirect, "soft" dependency of one of the other packages in the installer's package list. It's unclear why it is not being pulled in for the customer's builds.

              obudai@redhat.com Ondrej Budai
              akoutsou@redhat.com Achilleas Koutsou
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: