Bug 1931545

Summary: podman 3.0.1 ships with a v2 go module
Product: Red Hat Enterprise Linux 8 Reporter: Valentin Rothberg <vrothber>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Joy Pu <ypu>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.4CC: bbaude, ddarrah, dwalsh, jligon, jnovy, lfriedma, lmiksik, lsm5, mheon, pthomas, tsweeney, umohnani, ypu
Target Milestone: rcKeywords: Triaged
Target Release: 8.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-3.0.1-3.el8 or newer Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1933776 (view as bug list) Environment:
Last Closed: 2021-05-18 15:34:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1933776    

Description Valentin Rothberg 2021-02-22 16:32:58 UTC 
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
Comment 4 Daniel Walsh 2021-02-22 21:06:28 UTC 
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.
Comment 14 errata-xmlrpc 2021-05-18 15:34:31 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 (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