Bug 2221207

Summary:	RFE: catch "efibootmgr -C" error
Product:	Red Hat Enterprise Linux 7	Reporter:	Renaud Métrich <rmetrich>
Component:	leapp-repository	Assignee:	Leapp Notifications Bot <leapp-notifications-bot>
Status:	CLOSED MIGRATED	QA Contact:	upgrades-and-conversions
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.9	CC:	mportman, pstodulk
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-12 15:22:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Renaud Métrich 2023-07-07 13:34:39 UTC

Description of problem:

Customers upgrading VMWare VMs may face an issue were "efibootmgr -C" fails to create the new entry for the Leapp Upgrade kernel because of "No space left on device" (actor "efi_interim_fix"):
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
... leapp.workflow.InterimPreparation: Executing actor efi_interim_fix 
... leapp.workflow.InterimPreparation.efi_interim_fix: External command has started: ['/sbin/efibootmgr']
... leapp.workflow.InterimPreparation.efi_interim_fix: BootCurrent: 0005
... leapp.workflow.InterimPreparation.efi_interim_fix: BootOrder: 0005,0000,0001,0002,0003,0004
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0000* EFI Virtual disk (0.0)
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0001* EFI Virtual disk (1.0)
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0002* EFI VMware Virtual SATA CDROM Drive (0.0)
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0003* EFI Network
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0004* EFI Internal Shell (Unsupported option)
... leapp.workflow.InterimPreparation.efi_interim_fix: Boot0005* Red Hat Enterprise Linux
... leapp.workflow.InterimPreparation.efi_interim_fix: External command has finished: ['/sbin/efibootmgr']
... leapp.workflow.InterimPreparation.efi_interim_fix: External command has started: ['/sbin/efibootmgr', '-n', u'0005']
... leapp.workflow.InterimPreparation.efi_interim_fix: Could not set BootNext: No space left on device
... leapp.workflow.InterimPreparation.efi_interim_fix: Command ['/sbin/efibootmgr', '-n', u'0005'] failed with exit code 13.
... leapp.workflow.InterimPreparation.efi_interim_fix: External command has finished: ['/sbin/efibootmgr', '-n', u'0005']
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

The issue happens when VMWare VM has a too small NVRAM file.
It would be nice to point to the KCS I just wrote: https://access.redhat.com/solutions/7023631

This KCS is VMWare specific. If the issue happens on other hardware, then likely there is some Firmware issue to deal with.

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

all releases

How reproducible:

Always

Steps to Reproduce:
1. Create a VMWare VM at Hardware Level 13 in UEFI
2. Install RHEL7 and update it
3. Try to leapp it

Actual results:

See above

Expected results:

Error + KCS

Comment 3 Petr Stodulka 2023-07-10 08:59:13 UTC

Hi \o thanks for the report. We will documented in the KI section of the main documentation in the meanwhile.

Comment 4 RHEL Program Management 2023-09-12 14:45:46 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 5 RHEL Program Management 2023-09-12 15:22:30 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.