Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionSergii Golovatiuk
2020-12-07 20:34:58 UTC
There are cases when EFI is not disabled but not used as well. It means that /boot/efi will be mounted but it will be empty. So, leapp will fail with the following error
Building initram disk for kernel: 4.18.0-193.29.1.el8_2.x86_64 finished
###############################################################################
2020-12-05 03:18:19.233 INFO PID: 141387 leapp.workflow.InterimPreparation: Executing actor add_upgrade_boot_entry
2020-12-05 03:18:19.308 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has started: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upg
rade.x86_64', '-c', '/boot/grub2/grub.cfg']
2020-12-05 03:18:19.348 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has finished: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/grub2/grub.cfg']
2020-12-05 03:18:19.352 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has started: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg']
error opening /boot/efi/EFI/redhat/grub.cfg for read: No such file or directory
2020-12-05 03:18:19.370 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: Command ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] failed with exit code 1.
2020-12-05 03:18:19.378 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has finished: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg']
2020-12-05 03:18:19.403 INFO PID: 141387 leapp.workflow.InterimPreparation: Executing actor efi_interim_fix
2020-12-05 03:18:19.492 INFO PID: 141387 leapp.workflow.InterimPreparation: Starting stage After of phase InterimPreparation
2020-12-05 03:18:19.502 INFO PID: 141387 leapp.workflow: Workflow interrupted due to the FailPhase error policy
2020-12-05 03:18:19.520 INFO PID: 141387 leapp: Answerfile will be created at /var/log/leapp/answerfile
============================================================
ERRORS
============================================================
2020-12-05 03:18:19.381688 [ERROR] Actor: add_upgrade_boot_entry
Message: Cannot configure bootloader.
Summary:
Details: Command ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] failed with exit code 1.: error opening /boot/efi/EFI/redhat/grub.cfg for read: No such file or directory
============================================================
END OF ERRORS
============================================================
Debug output written to /var/log/leapp/leapp-upgrade.log
============================================================
REPORT
============================================================
To workaround the problem we just did the following workaround
[ -d /boot/efi ] && cp /boot/grub2/grub.cfg /boot/efi/EFI/redhat/grub.cfg
Was this bug encountered on the undercloud or overcloud? And the upgrade was from what to what? I'd like to understand what conditions put customer at risk of hitting this.
Thanks
CFields
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (leapp and leapp-repository bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:0569
There are cases when EFI is not disabled but not used as well. It means that /boot/efi will be mounted but it will be empty. So, leapp will fail with the following error Building initram disk for kernel: 4.18.0-193.29.1.el8_2.x86_64 finished ############################################################################### 2020-12-05 03:18:19.233 INFO PID: 141387 leapp.workflow.InterimPreparation: Executing actor add_upgrade_boot_entry 2020-12-05 03:18:19.308 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has started: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upg rade.x86_64', '-c', '/boot/grub2/grub.cfg'] 2020-12-05 03:18:19.348 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has finished: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/grub2/grub.cfg'] 2020-12-05 03:18:19.352 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has started: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] error opening /boot/efi/EFI/redhat/grub.cfg for read: No such file or directory 2020-12-05 03:18:19.370 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: Command ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] failed with exit code 1. 2020-12-05 03:18:19.378 DEBUG PID: 187752 leapp.workflow.InterimPreparation.add_upgrade_boot_entry: External command has finished: ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] 2020-12-05 03:18:19.403 INFO PID: 141387 leapp.workflow.InterimPreparation: Executing actor efi_interim_fix 2020-12-05 03:18:19.492 INFO PID: 141387 leapp.workflow.InterimPreparation: Starting stage After of phase InterimPreparation 2020-12-05 03:18:19.502 INFO PID: 141387 leapp.workflow: Workflow interrupted due to the FailPhase error policy 2020-12-05 03:18:19.520 INFO PID: 141387 leapp: Answerfile will be created at /var/log/leapp/answerfile ============================================================ ERRORS ============================================================ 2020-12-05 03:18:19.381688 [ERROR] Actor: add_upgrade_boot_entry Message: Cannot configure bootloader. Summary: Details: Command ['/usr/sbin/grubby', '--remove-kernel', '/boot/vmlinuz-upgrade.x86_64', '-c', '/boot/efi/EFI/redhat/grub.cfg'] failed with exit code 1.: error opening /boot/efi/EFI/redhat/grub.cfg for read: No such file or directory ============================================================ END OF ERRORS ============================================================ Debug output written to /var/log/leapp/leapp-upgrade.log ============================================================ REPORT ============================================================ To workaround the problem we just did the following workaround [ -d /boot/efi ] && cp /boot/grub2/grub.cfg /boot/efi/EFI/redhat/grub.cfg