Bug 2002670

Summary: [rhel-9.0.0beta] podman auto update fails to login to registry after podman upgrade to 3.2
Product: Red Hat Enterprise Linux 9 Reporter: Jindrich Novy <jnovy>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED CURRENTRELEASE QA Contact: Joy Pu <ypu>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 9.0CC: ajia, atomic-bugs, bbaude, dwalsh, jligon, jnovy, lmiksik, lsm5, mheon, pthomas, rik.theys, smccarty, tsweeney, umohnani, vrothber, ypu
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-3.3.1-8.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2000943
: 2005032 (view as bug list) Environment:
Last Closed: 2021-12-07 21:44:43 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: 2000943    
Bug Blocks: 2002591, 2005032    

Comment 2 Jindrich Novy 2021-09-09 13:24:13 UTC 
Can we get qa ack please?
Comment 4 Jindrich Novy 2021-09-09 13:25:33 UTC 
Justification from Valentin Rothberg:

The benefit of making this change after the deadline is to fix a regression.  Auto updates allows for using custom authentication files per container which is not working anymore.  The fix is minimal and non-intrusive, and I do not see a risk of causing issues by fixing the bug.

The commit in question for backporting is https://github.com/containers/podman/pull/11357/commits/de3920c0e970324f9d5238c13caf1020efefbd7f

Once we have an ACK, I will open a PR against v3.3.2 as suggested by Dan in comment #3.
Comment 11 Joy Pu 2021-09-29 16:19:16 UTC 
Test with podman-3.3.1-8.module+el9.0.0+12708+ede28c0e.x86_64 and it works as expected. So set this to verified.