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 1622646 - /boot/efi/EFI/redhat/grub.cfg does not get updated if /boot/grub2/grub.cfg exist on a uefi install.
Summary: /boot/efi/EFI/redhat/grub.cfg does not get updated if /boot/grub2/grub.cfg ex...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ondřej Lysoněk
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1556990
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-27 16:26 UTC by Dominik Rehák
Modified: 2019-12-06 16:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1556990
Environment:
Last Closed: 2019-12-06 16:06:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-performance tuned pull 220 0 'None' closed bootloader: Don't abort patching if grub.cfg is empty 2020-09-29 12:45:27 UTC

Comment 2 Jaroslav Škarvada 2018-08-28 08:56:36 UTC 
Maybe we should check timestamps and use the latest one.
Comment 3 Ondřej Lysoněk 2019-03-21 16:42:31 UTC 
(In reply to Jaroslav Škarvada from comment #2)
> Maybe we should check timestamps and use the latest one.

Is there a reason to do that? Currently we patch both the regular and the EFI grub.cfg, if they exist. Is that not a good enough solution? I think it's more reliable and works even if people switch between legacy and EFI mode.
Comment 4 Jaroslav Škarvada 2019-03-22 08:41:56 UTC 
(In reply to Ondřej Lysoněk from comment #3)
> (In reply to Jaroslav Škarvada from comment #2)
> > Maybe we should check timestamps and use the latest one.
> 
> Is there a reason to do that? Currently we patch both the regular and the
> EFI grub.cfg, if they exist. Is that not a good enough solution? I think
> it's more reliable and works even if people switch between legacy and EFI
> mode.

Yes, patching all is OK. Just the grub.cfg zero check has to be improved not to stop patching of the rest of grub config files.
Comment 5 Ondřej Lysoněk 2019-11-22 16:47:40 UTC 
Upstream PR:
https://github.com/redhat-performance/tuned/pull/220
Comment 6 Ondřej Lysoněk 2019-11-25 14:43:39 UTC 
(In reply to Ondřej Lysoněk from comment #5)
> Upstream PR:
> https://github.com/redhat-performance/tuned/pull/220

It got merged.
Comment 7 Tomáš Hozza 2019-12-06 16:06:28 UTC 
Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019. In this phase only qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.

This bug has been reviewed by Support and Engineering representative and does not meet the inclusion criteria for Maintenance Support 1 Phase. If this issue still exists in newer major version of Red Hat Enterprise Linux, it has been cloned there and work will continue in the cloned bug.

For more information about Red Hat Enterprise Linux Lifecycle, please see https://access.redhat.com/support/policy/updates/errata/
Comment 8 RHEL Program Management 2019-12-06 16:06:35 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain  the issue receives the proper prioritization with product and development management.

https://www.redhat.com/support/process/production/#howto
Note You need to log in before you can comment on or make changes to this bug.