This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2051889 - "Weak" grub2.cfg file generated on PPC64LE platform
Summary: "Weak" grub2.cfg file generated on PPC64LE platform
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: grub2
Version: 8.7
Hardware: ppc64le
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-08 09:58 UTC by Renaud Métrich
Modified: 2023-09-16 13:26 UTC (History)
7 users (show)

Fixed In Version: grub2-2.02-151.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-16 13:23:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch (1.46 KB, application/mbox)
2023-03-31 11:24 UTC, Marta Lewandowska 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4314 0 None Migrated None 2023-09-16 13:23:32 UTC
Red Hat Issue Tracker RHELPLAN-111449 0 None None None 2022-02-08 10:09:00 UTC

Description Renaud Métrich 2022-02-08 09:58:41 UTC 
Description of problem:

On PPC64LE platforms we disable GRUB_ENABLE_BLSCFG=true to force having a completely hardcoded grub2.cfg file with "menuentry" items.

This works fine except the $kernelopts variable is not designed as fallback in case grubenv is broken.

Following snippet is missing:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# The kernelopts variable should be defined in the grubenv file. But to ensure that menu
# entries populated from BootLoaderSpec files that use this variable work correctly even
# without a grubenv file, define a fallback kernelopts variable if this has not been set.
#
# The kernelopts variable in the grubenv file can be modified using the grubby tool or by
# executing the grub2-mkconfig tool. For the latter, the values of the GRUB_CMDLINE_LINUX
# and GRUB_CMDLINE_LINUX_DEFAULT options from /etc/default/grub file are used to set both
# the kernelopts variable in the grubenv file and the fallback kernelopts variable.
if [ -z "${kernelopts}" ]; then
  set kernelopts="..."
fi
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

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

grub2-2.02-106.el8

How reproducible:

Always

Steps to Reproduce:
1. Generate the file on PPC64le

  # grub2-mkconfig -o /tmp/foo

2. Check content

  # grep kernelopts /tmp/foo
	 linux /vmlinuz-4.18.0-147.el8.ppc64le $kernelopts $tuned_params
	 linux /vmlinuz-0-rescue-3199ef9eefd840ffb6e94a87b592a6ea $kernelopts


Actual results:

No fallback "if [ -z "${kernelopts}" ]; then ... fi" code

Expected results:

Fallback snippet from /etc/grub.d/10_linux found on x86_64 systems
Comment 2 Renaud Métrich 2023-03-21 09:45:54 UTC 
Hello,

It's now a long time I opened this and still nothing happened, even though the proposed fix is easy to implement.

Implementing such fix will definitely help getting less customer cases, when issue happens due to corrupted grubenv file.

Thank you for your understanding.

Renaud.
Comment 3 Marta Lewandowska 2023-03-24 13:24:46 UTC 
Hi Renaud,
you're right that it's been a long time. We have a test build that we will run tests on for regressions and other unanticipated issues. Clearly this won't make it into the next release, so we'll target 8.9 instead. Sorry about that, and thanks for understanding. :)
Comment 4 Marta Lewandowska 2023-03-31 11:24:01 UTC 
Created attachment 1954878 [details]
patch
Comment 5 Marta Lewandowska 2023-03-31 11:25:21 UTC 
Removing /boot/grub2/grubenv or doing grub2-editenv - set kernelopts=
and keeping GRUB_ENABLE_BLSCFG=true in /etc/default/grub
and rebooting, causes kernel to lose its cmdline.

Installing Renaud's fix and running grub2-mkconfig -o /boot/grub2/grub.cfg enables successful boot on ppc even in the absence of grubenv.
Comment 7 RHEL Program Management 2023-09-16 13:23:20 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 8 RHEL Program Management 2023-09-16 13:23:37 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.
Note You need to log in before you can comment on or make changes to this bug.