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:

When moving over to Podman 3.0, the go module in the source code remained on version 2.  We already bumped it to v3 in the main branch and the v3.0 branch of Podman and I think we should do the same for the v3.0.1-rhel branch, which is the stable for Podman v3.0.1 we will ship with RHEL 8.4.

The reason to also bump it for RHEL is to prevent any potential disruptions that may confuse Go clients into using a false version.  Also, since this specific version will be supported for a long time, bumping the version would simplify backporting fixes; the risk of merge conflicts is high without it.

PR to bump it in the v3.0.1-rhel branch.
https://github.com/containers/podman/pull/9471

Version-Release number of selected component (if applicable):


Podman v3.0.1

The main reason we want this change, is that it will be painful for us to back port for the next two years, since the main branch is moved to v3.  Making this change is very low risk and will benefit the engineering team greatly.

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: container-tools:rhel8 security, 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/RHSA-2021:1796