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:
The kernel_settings role will issue an error like 'configobj not found' on RHEL 8.6 managed hosts.  This only happens if the package `python3-configobj` is not already present on the host.
Version-Release number of selected component (if applicable):


How reproducible:
If the managed host is from a VM image which uses cloud-init, then python3-configobj is pulled in as a dependency.  So in order to reproduce, you must use on a managed host not using cloud-init, or otherwise having python3-configobj installed, or you must remove cloud-init and any leaf dependencies installed by cloud-init.  Also note that `yum erase cloud-init` or `yum remove cloud-init` DOES NOT remove these leaf dependencies, because something about the dependencies are installed at machine provisioning time.  So if you want to reproduce by removing cloud-init and dependencies, you have to manually find and remove them.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Note: This is due to a recent change in tuned in rhel 8.6 - they switched from using configobj to configparser.  kernel_settings did not have an explicit dependency on configobj.

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: rhel-system-roles), 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:2443