RHBA-2026:98551 - Bug Fix Advisory

Topic

An update for leapp-repository is now available for Red Hat Enterprise Linux 8.

Description

Repositories for leapp

Bug Fix(es) and Enhancement(s):

• Can't mount root filesystem when booting to the target system (live mode) (JIRA:RHEL-104379)
• Stream>RHEL: Update GRUB2 configuration (JIRA:RHEL-110712)
• IPU with FIPS in livemode fails due to missing .hmac (JIRA:RHEL-129571)
• All report messages to respect distro name (JIRA:RHEL-130948)
• Upgrading from RHEL 8 to 9 logrotate.timer is not enabled by default. (JIRA:RHEL-17361)
• the eth check is too simplistic and fails when customers have a persistent rule for eth devices (JIRA:RHEL-3370)
• leapp_resume fails when enforcing=1 was already set in the cmdline (JIRA:RHEL-162192)
• leapp upgrade crashes on RHEL 8.10 when repo URL includes + character (JIRA:RHEL-148631)
• leapp fails in reboot phase when LUKS devices are present, despite TPM2 is used for binding (JIRA:RHEL-145136)
• Upgrade requires a manual step, automation stops (live mode) (JIRA:RHEL-104384)
• Check for /var/run symlink during leapp preupgrade (JIRA:RHEL-76846)
• Services are executed during the selinux-autorelabel (JIRA:RHEL-60060)
• Live mode: update 'do-upgrade.sh' to reflect upstream changes (JIRA:RHEL-56040)
• leapp breaks in reboot phase on UEFI systems with /boot/efi on a Software Raid (JIRA:RHEL-36249)
• leapp fails in reboot phase when /dev/shm is a persistent file system (JIRA:RHEL-17842)
• Leapp 8>9: no inhibitor for some ifcfg files without NM_CONTROLLED=no + NM disabled, and network down post-reboot [8.10.z] (JIRA:RHEL-185508)
• Leapp can fail when /boot is a multipath (JIRA:RHEL-3289)
• leapp fails in reboot phase when a "nofail" mount point cannot be mounted (JIRA:RHEL-56176)
• Leapp upgrade failure from RHEL 8.10 to 9.8 during IPU builds testing in multipath system (JIRA:RHEL-162410)
• leapp fails in reboot phase when a temporary user mount is statically defined in /etc/fstab (JIRA:RHEL-16320)
• Rebase leapp-repository to v0.25.0 (rhel-8.10) (JIRA:RHEL-188369)
• UEFI boot entry created way too early on aarch64 on 8to9 upgrade (JIRA:RHEL-213986)
• Leapp fails while running "su - -c update-ca-trust" exit code 1 (JIRA:RHEL-50161)
• leapp hangs on reboot phase waiting for resume device on some systems installed in software raid (JIRA:RHEL-95495)

Solution

For details on how to apply this update, which includes the changes described in this advisory, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux for x86_64 8 x86_64
• Red Hat Enterprise Linux for IBM z Systems 8 s390x
• Red Hat Enterprise Linux for Power, little endian 8 ppc64le
• Red Hat Enterprise Linux for ARM 64 8 aarch64
• Red Hat Enterprise Linux for x86_64 - Extended Life Cycle 8.10 x86_64
• Red Hat Enterprise Linux for ARM 64 - Extended Life Cycle 8.10 aarch64
• Red Hat Enterprise Linux for Power, little endian - Extended Life Cycle 8.10 ppc64le
• Red Hat Enterprise Linux for IBM z Systems - Extended Life Cycle 8.10 s390x

Fixes

• RHEL-104379 - Can't mount root filesystem when booting to the target system (live mode)
• RHEL-110712 - Stream>RHEL: Update GRUB2 configuration
• RHEL-130948 - All report messages to respect distro name
• RHEL-17361 - Upgrading from RHEL 8 to 9 logrotate.timer is not enabled by default.
• RHEL-3370 - the eth check is too simplistic and fails when customers have a persistent rule for eth devices
• RHEL-162192 - leapp_resume fails when enforcing=1 was already set in the cmdline
• RHEL-145136 - leapp fails in reboot phase when LUKS devices are present, despite TPM2 is used for binding
• RHEL-104384 - Upgrade requires a manual step, automation stops (live mode)
• RHEL-76846 - Check for /var/run symlink during leapp preupgrade
• RHEL-60060 - Services are executed during the selinux-autorelabel
• RHEL-56040 - Live mode: update 'do-upgrade.sh' to reflect upstream changes
• RHEL-36249 - leapp breaks in reboot phase on UEFI systems with /boot/efi on a Software Raid
• RHEL-17842 - leapp fails in reboot phase when /dev/shm is a persistent file system
• RHEL-3289 - Leapp can fail when /boot is a multipath
• RHEL-56176 - leapp fails in reboot phase when a "nofail" mount point cannot be mounted
• RHEL-16320 - leapp fails in reboot phase when a temporary user mount is statically defined in /etc/fstab
• RHEL-188369 - Rebase leapp-repository to v0.25.0 (rhel-8.10)
• RHEL-50161 - Leapp fails while running "su - -c update-ca-trust" exit code 1
• RHEL-95495 - leapp hangs on reboot phase waiting for resume device on some systems installed in software raid

CVEs

(none)

References

(none)