2015146 – Leapp can fail when /boot is a multipath

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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.

Bug 2015146 - Leapp can fail when /boot is a multipath

Summary: Leapp can fail when /boot is a multipath

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	leapp-repository
Sub Component:
Version:	7.9
Hardware:	x86_64
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Leapp Notifications Bot
QA Contact:	upgrades-and-conversions
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-10-18 14:00 UTC by Christophe Besson
Modified:	2023-09-12 11:22 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-12 11:22:24 UTC
Target Upstream Version:
Embargoed:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	OAMG-6179	None	None	None	2021-12-02 17:03:55 UTC
Red Hat Issue Tracker	RHEL-3289	None	Migrated	None	2023-09-12 11:18:56 UTC
Red Hat Issue Tracker	RHELPLAN-100136	None	None	None	2021-10-18 14:04:48 UTC
Red Hat Knowledge Base (Solution)	6962799	None	None	None	2022-06-10 14:38:36 UTC

Description Christophe Besson 2021-10-18 14:00:37 UTC

Description of problem:
During the reboot step, Leapp is unable to mount /boot, it uses a wrong device name. After that, it is unable to proceed with the first actor (remove_grub_boot_entry).

Version-Release number of selected component (if applicable):
leapp-repository-0.14.0-4.el7_9.noarch

How reproducible:
Always for the customer.

Actual results:
~~~~~~~~~
[...]
Sep 28 03:57:49 localhost upgrade[3457]: mount: /dev/sdk2 is already mounted or /boot busy
Sep 28 03:57:49 localhost kernel: XFS (dm-17): Mounting V5 Filesystem
Sep 28 03:57:49 localhost upgrade[3457]: mount: mount point /boot/efi does not exist
Sep 28 03:57:49 localhost kernel: XFS (dm-17): Ending clean mount
Sep 28 03:57:49 localhost kernel: XFS (dm-18): Mounting V5 Filesystem
Sep 28 03:57:49 localhost kernel: XFS (dm-18): Ending clean mount
Sep 28 03:57:49 localhost kernel: XFS (dm-15): Mounting V5 Filesystem
Sep 28 03:57:49 localhost kernel: XFS (dm-15): Ending clean mount
Sep 28 03:57:49 localhost kernel: XFS (dm-16): Mounting V5 Filesystem
Sep 28 03:57:49 localhost kernel: XFS (dm-16): Ending clean mount
Sep 28 03:57:54 localhost upgrade[3457]: ==> Processing phase `InitRamStart`
Sep 28 03:57:54 localhost upgrade[3457]: ====> * remove_upgrade_boot_entry
Sep 28 03:57:54 localhost upgrade[3457]:         Remove boot entry for Leapp provided initramfs.
Sep 28 03:57:54 localhost upgrade[3457]: Process Process-165:
Sep 28 03:57:54 localhost upgrade[3457]: Traceback (most recent call last):
[...]
Sep 28 03:57:54 localhost upgrade[3457]:   File "/usr/lib/python2.7/site-packages/leapp/libraries/stdlib/__init__.py", line 188, in run
Sep 28 03:57:54 localhost upgrade[3457]:     result=result
Sep 28 03:57:54 localhost upgrade[3457]: CalledProcessError: Command ['/usr/sbin/grubby', '--remove-kernel=/boot/vmlinuz-upgrade.x86_64'] failed with exit code 1.
Sep 28 03:57:55 localhost upgrade[3457]: ==========================================================================================================
Sep 28 03:57:55 localhost upgrade[3457]: Actor remove_upgrade_boot_entry unexpectedly terminated with exit code: 1 - Please check the above details
Sep 28 03:57:55 localhost upgrade[3457]: ==========================================================================================================
[...]
~~~~~~~~~~~~~~

Additional info:
* The issue here is the fact /dev/sdk2 does not correspond to the boot partition
~~~
sda                                       8:0    0  100G  0 disk  
`-<WWID>     253:9    0  100G  0 mpath 
  |-<WWID>p1 253:10   0  256M  0 part  /boot/efi
  |-<WWID>p2 253:11   0  500M  0 part  /boot
 :
sdk                                       8:160  0  100G  0 disk  
`-<WWID>     253:9    0  100G  0 mpath 
  |-<WWID>p1 253:10   0  256M  0 part  /boot/efi
  |-<WWID>p2 253:11   0  500M  0 part  /boot
~~~

* From my understanding, it's a timing issue with multipathd. The customer have lots of disks behind an Hitachi storage array, and only /boot and /boot/efi are not part of LVM.
* Changing the fstab to use the /dev/mapper/path (with the wwids in this case) fixed the issue. The fstab entries have been reverted back once the system has been upgraded.

Comment 5 Christophe Besson 2023-02-14 16:34:36 UTC

This bug is blocked by:

    Bug 2169770 - System boot hangs after mounting /sysroot when multipath is enabled in the initramfs
    https://bugzilla.redhat.com/show_bug.cgi?id=2169770

Comment 7 RHEL Program Management 2023-09-12 11:06:45 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 8 RHEL Program Management 2023-09-12 11:22:24 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.

Note You need to log in before you can comment on or make changes to this bug.