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 2181380 - Include High Risk Inhibitor In Leapp Report if Boot Disk's Embedding Area Too Small for grub2-install
Summary: Include High Risk Inhibitor In Leapp Report if Boot Disk's Embedding Area Too...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Leapp Notifications Bot
QA Contact: upgrades-and-conversions
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-23 22:39 UTC by ckrell
Modified: 2023-09-12 13:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-12 13:24:53 UTC
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-8747 0 None None None 2023-03-23 22:41:16 UTC
Red Hat Issue Tracker   RHEL-3341 0 None Migrated None 2023-09-12 13:20:56 UTC
Red Hat Issue Tracker RHELPLAN-152948 0 None None None 2023-03-23 22:41:05 UTC

Description ckrell 2023-03-23 22:39:49 UTC 
Description of problem:

If you attempt a leapp upgrade and the boot disk's embedded area is too small (ie. the boot disk's first partition starts on a low sector number such as 63) for the core.img file then the grub2-install fails during the upgrade kernel portion of the upgrade. Normally the first partition starts on 2048.

grub2-install error example during upgrade kernel:
~~~
2023-03-21 10:18:41.722 INFO     PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: GRUB is installed on /dev/sda
2023-03-21 10:18:41.728 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: External command has started: ['grub2-install', u'/dev/sda']
2023-03-21 10:18:41.753 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: Installing for i386-pc platform.
2023-03-21 10:18:42.728 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: grub2-install: warning: ../grub-core/partmap/msdos.c:401:your core.img is unusually large.  It won't fit in the embedding a
rea.
2023-03-21 10:18:42.735 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: grub2-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However,
 blocklists are UNRELIABLE and their use is discouraged..
2023-03-21 10:18:42.741 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: grub2-install: error: will not proceed with blocklists.
2023-03-21 10:18:42.747 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: Command ['grub2-install', u'/dev/sda'] failed with exit code 1.
2023-03-21 10:18:42.759 DEBUG    PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: External command has finished: ['grub2-install', u'/dev/sda']
2023-03-21 10:18:42.766 WARNING  PID: 70738 leapp.reporting: Stable Key report entry not provided, dynamically generating one - 54ba8c51e17b2088df653f3df0f1ae490f9ead88
2023-03-21 10:18:42.779 WARNING  PID: 70738 leapp.workflow.RPMUpgrade.update_grub_core: GRUB core update on /dev/sda failed
~~~

After rebooting this leads to a can't boot scenario where it fails to boot at the grub rescue shell with a message:
~~~
error: symbol 'grub_calloc' not found. 
Entering rescue mode...
grub rescue>
~~~
or
~~~
error: symbol 'grub_real_boot_time' not found.
~~~

Version-Release number of selected component (if applicable):
leapp-0.15.0-2.el7_9.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Make a RHEL 7 boot disk with the first partition starting on sector 75 or another early sector (to do this I had to create the partitions using a RHEL 6 version of fdisk).
2. leapp upgrade
3. Reboot to upgrade kernel, during this you may witness the grub2-install failure
4. Reboot again and see the boot failure to grub rescue shell

Actual results:
No inhibitor with messages about the boot device's embedded area being too small so the system fails to boot to grub rescue after the upgrade.

Expected results:
Inhibitor with message that the boot disk has insufficient space in the embedded area to perform grub2-install so that we can catch this before a can't boot scenario.
Comment 6 RHEL Program Management 2023-09-12 13:18:53 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 7 RHEL Program Management 2023-09-12 13:24:53 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.