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.
Bug 2005032 - [rhel-9.0.0beta] podman auto update fails to login to registry after podman upgrade to 3.2 [rhel-9.0.0]
Summary: [rhel-9.0.0beta] podman auto update fails to login to registry after podman u...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: podman
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On: 2002670
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 15:06 UTC by RHEL Program Management Team
Modified: 2022-05-17 12:57 UTC (History)
15 users (show)

Fixed In Version: podman-4.0.0-0.7.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2002670
Environment:
Last Closed: 2022-05-17 12:42:09 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-97483 0 None None None 2021-09-17 16:19:46 UTC
Red Hat Product Errata RHBA-2022:2379 0 None None None 2022-05-17 12:42:59 UTC

Comment 1 Tom Sweeney 2021-09-16 17:52:26 UTC 
Jindrich, I think you have everything that you need for this one, please see Backport PR: https://github.com/containers/podman/pull/11522

If not, please let me know.
Comment 6 Joy Pu 2021-11-08 10:51:39 UTC 
Test with podman-3.4.2-0.2.el9.x86_64 and it works as expected. The auth.json can work with podman auto-update. So set this to verified. Details:
1. Create a container with labels
 # podman create --authfile=/root/auth.json --label "io.containers.autoupdate=image" --label "io.containers.autoupdate.authfile=/root/auth.json" --name test-auto localhost:5000/testauto top
2. generate the systemd file
# podman generate systemd --new --files --name test-auto
3. start the service
# systemctl daemon-reload
# systemctl start container-test-auto
4. Use auto-update to update the image
# podman auto-update
Trying to pull localhost:5000/testauto:latest...
Getting image source signatures
Copying blob f3ac2f942260 skipped: already exists  
Copying config 9617696764 done  
Writing manifest to image destination
Storing signatures
UNIT                         CONTAINER                 IMAGE                    POLICY      UPDATED
container-test-auto.service  c311ad227039 (test-auto)  localhost:5000/testauto  registry    true
Comment 8 errata-xmlrpc 2022-05-17 12:42:09 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 (new packages: podman), 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/RHBA-2022:2379
Note You need to log in before you can comment on or make changes to this bug.