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.
.The `podman_registries_conf` variable now configures `unqualified-search-registries` field correctly
Previously, after configuring the `podman_registries_conf` variable, the `podman` RHEL System Role failed. Consequently, `unqualified-search-registries = ["registry.access.redhat.com"]` setting was not generated in the `/etc/containers/registries.conf.d/50-systemroles.conf` file. With this update, this problem has been fixed.
Description of problem:
I'm unable to use the podman_registries_conf variable to set the unqualified-search-registries setting.
Version-Release number of selected component (if applicable):
Automation Hub release of RHEL system roles: redhat.rhel_system_roles-1.21.1
How reproducible:
Every time
Steps to Reproduce:
Configure the podman_registries_conf variable and run the podman role:
podman_registries_conf:
unqualified-search-registries: ["registry.access.redhat.com"]
Actual results:
The role fails when run:
TASK [redhat.rhel_system_roles.podman : Update registries config file] **************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'list object' has no attribute 'registry.access.redhat.com'
fatal: [rhel9-server1.example.com]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'list object' has no attribute 'registry.access.redhat.com'"}
Expected results:
I would expect this to create the /etc/containers/registries.conf.d/50-systemroles.conf with the following:
unqualified-search-registries = ["registry.access.redhat.com"]
Additional info:
It appears that the role only supports configuring podman_registries_conf options that are under a namespace such as:
[namespace]
option = value
However, the unqualified-search-registries setting is a global setting that isn't under a namespace. For more info, see "man containers-registries.conf"
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 (rhel-system-roles 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/RHEA-2023:6390
Description of problem: I'm unable to use the podman_registries_conf variable to set the unqualified-search-registries setting. Version-Release number of selected component (if applicable): Automation Hub release of RHEL system roles: redhat.rhel_system_roles-1.21.1 How reproducible: Every time Steps to Reproduce: Configure the podman_registries_conf variable and run the podman role: podman_registries_conf: unqualified-search-registries: ["registry.access.redhat.com"] Actual results: The role fails when run: TASK [redhat.rhel_system_roles.podman : Update registries config file] ************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'list object' has no attribute 'registry.access.redhat.com' fatal: [rhel9-server1.example.com]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'list object' has no attribute 'registry.access.redhat.com'"} Expected results: I would expect this to create the /etc/containers/registries.conf.d/50-systemroles.conf with the following: unqualified-search-registries = ["registry.access.redhat.com"] Additional info: It appears that the role only supports configuring podman_registries_conf options that are under a namespace such as: [namespace] option = value However, the unqualified-search-registries setting is a global setting that isn't under a namespace. For more info, see "man containers-registries.conf"