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.
DescriptionPhilipp Trulson
2022-11-08 13:18:51 UTC
Description of problem:
We are using podman on CentOS Stream 9 for our CI infrastructure. Podman 4.2.1 was released over 2 months ago and contains a critical fix for us, however it hasn't arrived in the package repos yet. We specifically chose Stream to get updates faster - can you maybe explain the update schedule/policy for the whole podman/buildah/skopeo stack? Is there some kind of testing repo?
It would be really great if updates for this would be pushed faster.
Thanks for the quick reply Jindrich! For future reference - does it always take 2 months for paperwork? Did it take longer because you were busy/there were issues with packaging? We just want to know what delay to expect for future releases.
Phillip, there are multiple moving parts, e.g. currently failing gating tests. These need to get addressed before the new podman-4.3.0 can appear in c9s so that only stable content in c9s. I will update this bug once these are no longer an issue - which means you can update to podman-4.3.0 in c9s. If you'd like to test 4.3.0 and newer container-tools I suggest to try Fedora. Thank you for understanding.
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 (Moderate: podman security and bug fix 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/RHSA-2023:2282