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 2055313 - Creating a pod uses bad infra_image registry in podman
Summary: Creating a pod uses bad infra_image registry in podman
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 16:42 UTC by Matt Mezynski
Modified: 2023-09-18 04:32 UTC (History)
17 users (show)

Fixed In Version: podman-4.0.3-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-22 15:38:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112619 0 None None None 2022-02-16 16:44:53 UTC

Comment 6 Mario Trangoni 2022-03-08 11:38:08 UTC 
As I am running a VM in china and k8s.gcr.io is blocked there, I faced this issue, and was about to open a dup.

# grep infra_image /usr/share/containers/containers.conf
#infra_image = "k8s.gcr.io/pause:3.4.1"
infra_image = "registry.access.redhat.com/ubi8/pause"

Starting a pod with "podman pod create"
initializing source docker://k8s.gcr.io/pause:3.5: pinging container registry k8s.gcr.io: Get "http://k8s.gcr.io/v2/": dial tcp 108.177.125.82:80: i/o timeout
Error: repository name must have at least one component

Steps to Reproduce:
1. podman pod create
2. podman ps -a --pod

Expected results:
As of previous podman version 3.3.1,
# podman pod create
4cbeba590b7bfa834f2726c63b3a4b6046e01d0bdb1e4e4932371fd793920be9
# podman ps -a --pod
CONTAINER ID  IMAGE                                         COMMAND               CREATED        STATUS          PORTS                                                                         NAMES                                       POD ID        PODNAME
852d4453e640  registry.access.redhat.com/ubi8/pause:latest                        9 seconds ago  Created                                                                                       4cbeba590b7b-infra                          4cbeba590b7b  sharp_williams

Additional info:
As a workaround I had to run, 
dnf downgrade podman containers-common runc for downgrading to 3.3.1
Comment 7 ranjith.parasuraman 2022-04-29 19:47:16 UTC 
Hi,

I am too facing the same problem when creating pod with YAML file.

DEBU[0001] container "db6cf2c7489636bef98fb07238e5a486192c396290c0361fdbad80f8d5ee7cc8" has run directory "/tmp/podman-run-4793/containers/overlay-containers/db6cf2c7489636bef98fb07238e5a486192c396290c0361fdbad80f8d5ee7cc8/userdata"
DEBU[0001] Pulling image  (policy: newer)
Error: repository name must have at least one component


do we have any workaround or fix for this issue. It prevent the POD from getting started.
Comment 9 Tom Sweeney 2022-05-03 22:15:14 UTC 
@asreddy This was not completed until Podman v4.0 and it was not backported in time to make RHEL 8.5 and it is closed now.  Given that, I'm going to set this BZ to POST and will ask @jnovy to take care of any further BZ or packaging needs.  This is fixed in RHEL 8.6 and Podman v4.0.
Comment 21 Red Hat Bugzilla 2023-09-18 04:32:09 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.