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.
Description of problem:
1) Log in to the registry, use port number in login URL
[root@amf037-beta8 ~]# podman login docker-krk.mot-solutions.com:443
Username: <user>
Password: <password>
Login Succeeded!
2) Pull the image. Of course put port number in registry URL:
[root@amf037-beta8 ~]# podman pull docker-krk.mot-solutions.com:443/msi/mep/v2/bare:2.1.35
Trying to pull docker-krk.mot-solutions.com:443/msi/mep/v2/bare:2.1.35...
Getting image source signatures
Copying blob 7eaf9c8d33dd done
Copying blob cc123b47064d done
Copying blob 15b0272cc322 done
Copying config 335d150008 done
Writing manifest to image destination
Storing signatures
335d1500086a42706efbb7e5e4623eb69064deb653845964066041466cff02ec
3) List pulled images.
[root@amf037-beta8 ~]# podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker-krk.mot-solutions.com 443/msi/mep/v2/bare:2.1.35 335d1500086a 4 days ago 165 MB
registry.access.redhat.com/rhel7 latest 9da37a681956 9 days ago 215 MB
Note displayed image TAG: 443/msi/mep/v2/bare:2.1.35
Correct tag is 2.1.35
If we provide port number in URL everything after first ":" is shown as a tag. Displayed tag is incorrect.
Version-Release number of selected component (if applicable):
ersion: 2.0.0-rc7
API Version: 1
Go Version: go1.14.2
Built: Thu Jan 1 01:00:00 1970
OS/Arch: linux/amd64
How reproducible:
100%
Steps to Reproduce:
Provided in description
Actual results:
Expected results:
Additional info:
Comment 1Valentin Rothberg
2020-08-13 12:02:39 UTC
The issue has been fixed in Podman v2.0.4 (see below), so I think we can close?
######################
~ $ /usr/bin/podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker-krk.mot-solutions.com:443/msi/mep/v2/bare 2.1.35 ec9293436c2e 2 years ago 3.67 kB
~ $ /usr/bin/podman version
Version: 2.0.4
API Version: 1
Go Version: go1.14.6
Built: Thu Jan 1 01:00:00 1970
OS/Arch: linux/amd64
######################
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-2020:4694