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.

Created attachment 1539178 [details]
pstree

Description of problem:

While performing upgrade from RHEL7 to RHEL8 "grub2-tools" scriptlet is taking always about 20 minutes to complete.

Version-Release number of selected component (if applicable):

grub2-tools-1:2.02-65.el8.x86_64

How reproducible:

Upgrade RHEL 7 to RHEL 8.


Steps to Reproduce:
1. leapp upgrade
2. reboot
3. watch upgrade process in console  

Actual results:

"grub2-tools" scriptlet is taking always about 20 minutes to complete.

Expected results:

"grub2-tools" scriptlet finishes in reasonable amount of time

Additional info:

Attached pstree. Last 3 processes are looping. It looks like the vgs command itself is having issue however that should not cause the process to take 20 mins. "vgs" strace attached too.

Created attachment 1539179 [details]
vgs strace

Created attachment 1539181 [details]
vgs_cmd_output

After we made udev db accessible the issue is gone. It should however not take for grub2-tools 20 minutes to upgrade on machine with one storage device.

My customer is hitting the same issue (grub2-tools bug) even though they have the above leapp-repository version (leapp-repository-0.8.1-2.el7_6.noarch) installed.  

We've attempted to try to add the following options to break the rd boot process but the upgrade process still hangs and doesn't break out:

 rd.upgrade.debug rd.upgrade.break=leapp-upgrade


Reference case:  https://access.redhat.com/support/cases/02485812 


We have run out of ideas at this point.  Is there anything else we can try?

(In reply to Michal Reznik from comment #4)
> After we made udev db accessible the issue is gone. It should however not
> take for grub2-tools 20 minutes to upgrade on machine with one storage
> device.

This looks like a duplicate of Bug #1712456.

Ack, root cause is the same. Closing...

*** This bug has been marked as a duplicate of bug 1712456 ***