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.
Description of problem:
zipl does not support variables. Old versions of tuned result in $tuned_params being set in the config file. While the new version of tuned does not have this issue, the $tuned_params syntax is not removed when the system is updated, requiring manual intervention to remove the $tuned_params for the existing BLS file
Version-Release number of selected component (if applicable):
tuned-2.15.0-2.el8.noarch
kernel-core-4.18.0-305.el8.s390x
How reproducible:
Always
Steps to Reproduce:
1. Install a RHEL 8.2 s390x system with tuned
2. Update the system
Actual results:
The updated kernel entry still has the $tuned_params because it is still in the old kernel entry cmdline
Expected results:
The updated kernel entry should not have $tuned_params because zipl does not support variables in zipl
Additional info:
During the /bin/kernel-install script /usr/lib/kernel/install.d/92-tuned.install gets called, and that is what initially had the issue. It appears that now that is resolved:
# The zipl bootloader doesn't support variables
ARCH=`uname -m`
[ "${ARCH:0:4}" = "s390" ] && exit 0
But still $tuned_params is kept from the old cmdline. This issue may be a bug with some other package, but for now I'm opening it against tuned, feel free to move it if it's believed that it should be resolved somewhere else.
Comment 1Jaroslav Škarvada
2021-11-02 15:55:46 UTC
I think it needs explicit removal in the kernel-install scriptlet provided by TuneD, otherwise it will be automatically copied from older files with each update.
Comment 4Jaroslav Škarvada
2022-02-01 21:33:32 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 (tuned bug fix and enhancement update), 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:2106
Description of problem: zipl does not support variables. Old versions of tuned result in $tuned_params being set in the config file. While the new version of tuned does not have this issue, the $tuned_params syntax is not removed when the system is updated, requiring manual intervention to remove the $tuned_params for the existing BLS file Version-Release number of selected component (if applicable): tuned-2.15.0-2.el8.noarch kernel-core-4.18.0-305.el8.s390x How reproducible: Always Steps to Reproduce: 1. Install a RHEL 8.2 s390x system with tuned 2. Update the system Actual results: The updated kernel entry still has the $tuned_params because it is still in the old kernel entry cmdline Expected results: The updated kernel entry should not have $tuned_params because zipl does not support variables in zipl Additional info: During the /bin/kernel-install script /usr/lib/kernel/install.d/92-tuned.install gets called, and that is what initially had the issue. It appears that now that is resolved: # The zipl bootloader doesn't support variables ARCH=`uname -m` [ "${ARCH:0:4}" = "s390" ] && exit 0 But still $tuned_params is kept from the old cmdline. This issue may be a bug with some other package, but for now I'm opening it against tuned, feel free to move it if it's believed that it should be resolved somewhere else.