Bug 2185890 - IPU 7->8: wrong grubenv should inhibit upgrade
Summary: IPU 7->8: wrong grubenv should inhibit upgrade
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Leapp Notifications Bot
QA Contact: upgrades-and-conversions
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-11 14:15 UTC by Manuel Moran
Modified: 2023-07-31 07:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-8855 0 None None None 2023-04-11 14:17:54 UTC
Red Hat Issue Tracker RHELPLAN-154394 0 None None None 2023-04-11 14:17:45 UTC

Description Manuel Moran 2023-04-11 14:15:11 UTC
Description of problem:

During tests for https://bugzilla.redhat.com/show_bug.cgi?id=2159288 we found another grubenv configuration that could also make leapp upgrade fail.

How reproducible:
Always

Steps to Reproduce:
1. Get a 7.9 machine, install leapp-upgrade, run leapp preupgrade until it has no inhibitors and the report is successful
2. cd into the directory where grubenv is located
3. execute:

truncate --size=1023 grubenv
echo -n 'a' >> grubenv

4. run leapp preupgrade (it does not inhibit)
5. run leapp upgrade (it works). 
6. reboot

Actual results:
On reboot, the wrong grub entry is selected by default. If the correct entry is manually selected (upgrade initramfs), the machine ends up in emergency shell.

Expected results:
Inhibit leapp upgrade if such a format is found in grubenv.

Additional info:
Test MR (the test is already written and for now the test case will be commented out until this is resolved): https://gitlab.cee.redhat.com/oamg/leapp-tests/-/merge_requests/214


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