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.

Bug 1748019

Summary: Broken upgrade for non-intel arches beause of wrong efi provides
Product: Red Hat Enterprise Linux 7 Reporter: Petr Stodulka <pstodulk>
Component: grub2Assignee: Bootloader engineering team <bootloader-eng-team>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: urgent Docs Contact:
Priority: high    
Version: 7.8CC: bgollahe, fmartine, jhlavac, jstodola, leapp-notifications, mbocek, mgazdik, rcadova, tpelka, vfeenstr, vsokol
Target Milestone: rcKeywords: Upgrades, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: grub2-2.02-0.81.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1752486 (view as bug list) Environment:
Last Closed: 2020-03-31 20:07:50 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:
Bug Depends On:    
Bug Blocks: 1752486    
Attachments:
Description Flags
Patch none

Description Petr Stodulka 2019-09-02 13:38:50 UTC
Created attachment 1610774 [details]
Patch

Description of problem:
On the RHEL 7 systems, the grub2-tools rpm provides (and obsoletes) the grub2-tools-efi capability on all architectures. Regarding the discussion we had with jhlavac, this seems to be wrong as EFI isn't provided on non-intel architectures (correct me if  I am wrong). Because of this provides, we are not able to calculate upgrade RPM transaction to RHEL 8, because the capability is not provided anymore on RHEL 8 systems for non-intel architectures.


Actual results:
grub2-tools provides grub2-tools-efi on non-intel architectures

Expected results:
grub2-tools provide grub2-tools-efi only on intel architectures

Additional info:
Possible patch in the attachement. I found in th arch even the %{efi_arch} macro but it's used only once and everywhere else the x86_64 arch is used for similar purposes.

We need the fix released in RHEL ALT 7.6 - in this case it means z-stream.

Comment 30 Jan Stodola 2020-01-28 15:44:14 UTC
grub2-tools-2.02-0.81.el7 no longer provides grub2-tools-efi on non-x86_64 architectures (ppc64 and ppc64le), x86_64 still provides grub2-tools-efi as requested.
There was no regression found during upgrade testing (from RHEL-7.7 to the latest 7.8).

Moving this bug to VERIFIED.

Comment 32 errata-xmlrpc 2020-03-31 20:07:50 UTC
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, 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-2020:1161