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 2050877 - [lorax] Do not remove the nvram kernel module from install.img
Summary: [lorax] Do not remove the nvram kernel module from install.img
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: lorax
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-04 20:13 UTC by Jan Stodola
Modified: 2022-05-17 12:50 UTC (History)
0 users

Fixed In Version: lorax-34.9.14-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:34:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-111191 0 None None None 2022-02-04 20:17:13 UTC
Red Hat Issue Tracker RTT-4215 0 None None None 2022-02-04 22:44:24 UTC
Red Hat Issue Tracker RTT-4216 0 None None None 2022-02-04 22:44:28 UTC
Red Hat Product Errata RHBA-2022:2345 0 None None None 2022-05-17 12:34:05 UTC

Description Jan Stodola 2022-02-04 20:13:32 UTC 
Description of problem:
The nvram kernel module is not included in install.img on ppc64le.
The bootlist command then prints errors during the installation (ignore the printf messages):

INFO:program:Running... bootlist -m normal -o /dev/mapper/mpatha1
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/sbin/bootlist: line 277: printf: 0x: invalid hex number
INFO:program:/usr/sbin/nvram: ERROR: cannot open "/dev/nvram": No such device
INFO:program:/usr/sbin/nvram: ERROR: cannot open "/dev/misc/nvram": No such file or directory
INFO:program:Could not update bootlist!

In the lorax build log from compose RHEL-9.0.0-20220203.0 I can see that all except of a few modules are being removed:
...
template line 42: removekmod drivers/char --allbut virtio_console hw_random virtio-rng ipmi hmcdrv
...

Location and size of the kernel module on the installed system:
[root@ibm-p9z-20-lp14 ~]# ls -lh /lib/modules/5.14.0-52.el9.ppc64le/kernel/drivers/char/nvram.ko.xz
-rw-r--r--. 1 root root 3.7K Feb  1 12:58 /lib/modules/5.14.0-52.el9.ppc64le/kernel/drivers/char/nvram.ko.xz
[root@ibm-p9z-20-lp14 ~]#

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220203.0
lorax-34.9.11-1.el9
lorax-templates-rhel-9.0-32.el9

How reproducible:
always

Steps to Reproduce:
1. run "modprobe nvram" in the installation environment

Actual results:
The nvram kernel module is not loaded.

Expected results:
The module is loaded successfully.

Additional info:
This problem was originally noticed in bug 2017652.
Comment 1 Jan Stodola 2022-02-21 10:49:21 UTC 
runtime-cleanup.tmpl from lorax-templates-generic-34.9.14-1.el9 keeps the nvram module:

removekmod drivers/char --allbut virtio_console hw_random \
                                  virtio-rng ipmi hmcdrv nvram

Marking as Verified:Tested
Comment 5 Jan Stodola 2022-02-23 13:51:24 UTC 
Checked that lorax-34.9.14-1.el9 is in nightly compose RHEL-9.0.0-20220223.1

Moving to VERIFIED.
Comment 7 errata-xmlrpc 2022-05-17 12:34:03 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 (new packages: lorax), 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-2022:2345
Note You need to log in before you can comment on or make changes to this bug.