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 1644438 - fwupdate-efi conflicts with grub2-common
Summary: fwupdate-efi conflicts with grub2-common
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: fwupdate
Version: 7.6
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Erico Nunes
URL:
Whiteboard:
Depends On: 1578425
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-30 20:20 UTC by jcastran
Modified: 2023-03-24 14:19 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1578425
Environment:
Last Closed: 2020-08-27 15:41:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3682321 0 None None None 2018-11-08 16:28:47 UTC

Comment 3 BloodyIron 2018-11-01 20:07:43 UTC 
On 7.5 I was able to resolve this by

1. Installing grub2-common by itself
2. Then trying to install fwupdate-efi by itself

This then seems to have cleared the blocker for me. Try this out? :)
Comment 4 Anthony Jones 2018-11-06 12:16:34 UTC 
I attempted the work around. was able to install the grub2-common by itself but not the fwupdate-efi. so, currently I am still stuck and unable to update any security patches.
Comment 5 Anthony Jones 2018-11-06 12:29:14 UTC 
ok, ran subscription-manager release --unset redid the seperate installs and worked..
Comment 6 jcastran 2018-11-06 14:41:15 UTC 
Restating the issue:

This will not affect RHEL 7.6 fresh installs as that will come with the updated grub2-common. fwupdate-efi conflicts with all versions of grub2-common below grub2-common-2.02-0.76.el7.noarch currently. 


 # rpm -q grub2-common
    grub2-common-2.02-0.65.el7_4.2.noarch

 # yum groupinstall "Server with GUI"
    Transaction check error:
      file /boot/efi/EFI/redhat from install of fwupdate-efi-12-5.el7.x86_64 conflicts with file from package grub2-common-1:2.02-0.65.el7_4.2.noarch

 # yum install fwupdate-efi
    Transaction check error:
      file /boot/efi/EFI/redhat from install of fwupdate-efi-12-5.el7.x86_64 conflicts with file from package grub2-common-1:2.02-0.65.el7_4.2.noarch


*** Updating grub2-common will workaround this issue allowing customers to install Server with GUI or fwupdate-efi as required ***

 # yum update grub2-common
 # rpm -q grub2-common
   grub2-common-2.02-0.76.el7.noarch
 # yum install fwupdate-efi
Comment 7 Tomas Popela 2020-08-27 14:42:24 UTC 
Closing the bug as the attached customer case is closed.
Note You need to log in before you can comment on or make changes to this bug.