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.
DescriptionChristophe Besson
2022-09-30 11:34:59 UTC
Description of problem:
During an IPU 7>8, customer reported RHEL 8.6 fails stalls at reboot.
Checking the logs, it appears:
- the upgrade images have not been removed from /boot, explaining why it always reboots on this.
- rebooting on the RHEL 7.9 kernel, the OS seems to be correctly upgraded anyway (rpms are updated and /etc/redhat-release shows 8.6).
- no el8 kernel boot entry
The sosreport shows they have 40 disks with multipath and lpfc nics.
However sda where resides the rootfs, /boot and /boot/efi is not a mpath.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 558.4G 0 disk
|-sda1 8:1 0 200M 0 part /boot/efi
|-sda2 8:2 0 500M 0 part /boot
`-sda3 8:3 0 557.7G 0 part
|-rhel-root 253:0 0 50G 0 lvm /
|-rhel-swap 253:1 0 4G 0 lvm [SWAP]
Version-Release number of selected component (if applicable):
leapp-upgrade-el7toel8-0.16.0-4.el7_9
How reproducible:
Always for the customer.
Cannot reproduce internally.
Actual results:
$ grep -e leapp.workflow.Preparation.remove_boot_files -e sda2 0020-leapp-logs.tar/leapp/leapp-upgrade.log | grep localhost | head -n5
Sep 20 00:56:40 localhost kernel: sda: sda1 sda2 sda3
Sep 20 00:59:02 localhost upgrade[4157]: 2022-09-19 17:59:02.297 ERROR PID: 862 leapp.workflow.Preparation.remove_boot_files: Could not remove /boot/vmlinuz-upgrade.x86_64: [Errno 2] No such file or directory: '/boot/vmlinuz-upgrade.x86_64'.
Sep 20 00:59:02 localhost upgrade[4157]: 2022-09-19 17:59:02.362 ERROR PID: 862 leapp.workflow.Preparation.remove_boot_files: Could not remove /boot/initramfs-upgrade.x86_64.img: [Errno 2] No such file or directory: '/boot/initramfs-upgrade.x86_64.img'.
Sep 20 01:21:09 localhost kernel: XFS (sda2): Mounting V4 Filesystem <===
Sep 20 01:21:21 localhost kernel: XFS (sda2): Ending clean mount
Additional info:
- Need to request an sosreport taken on the upgraded OS, with the leapp.db.
- It seems replacing the UUIDs by the device names in /etc/fstab didn't help to move forward.
- Trying to hack the leapp dracut do-upgrade script to introduce a delay and force the mount of /boot didn't help, customer reported "/dev/sda2 can't open blockdev".
- Only workaround for now: fix manually the issue after the IPU (outlines: reboot on el7 kernel, remove upgrade imgs from /boot, reinstall the el8 kernel and check the grub.cfg and bls entries are correct).
Comment 5RHEL Program Management
2023-09-12 12:27:28 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-09-12 13:25:37 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.