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.

Bug 1430706

Summary: atomic pull registry confusion
Product: Red Hat Enterprise Linux 7 Reporter: Marko Myllynen <myllynen>
Component: atomicAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED DUPLICATE QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: ajia, amurdaca, bbaude, ddarrah, dwalsh, fkluknav, miabbott
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-03 14:31:19 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:

Description Marko Myllynen 2017-03-09 11:31:38 UTC 
Description of problem:
[root@atom ~]# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED       SIZE
[root@atom ~]# atomic pull rhel7/etcd
Image rhel7/etcd is being pulled to docker ...
Pulling registry.access.redhat.com/rhel7/etcd:latest ...
Copying blob sha256:154dc369ca0dfabd18ddeca63a8bced0dfaefaa0b2cd7cb6ec9513423d863652
...
Writing manifest to image destination
Storing signatures
 5.89 KB / 5.89 KB [===========================================================]
[root@atom ~]# docker images
REPOSITORY             TAG                 IMAGE ID            CREATED             SIZE
docker.io/rhel7/etcd   latest              77edbd3745c7        9 days ago          233.1 MB
[root@atom ~]# 

Note the discrepancy in atomic pull output compared to docker images output wrt the source registry.

Version-Release number of selected component (if applicable):
7.3.2
Comment 2 Alex Jia 2017-03-10 06:55:00 UTC 
In 7.3.2, atomic pull will search/download image from "registry-1.docker.io" and "registry.access.redhat.com" registry together.

[root@atomic-host-test-986 cloud-user]# atomic --debug pull rhel7/etcd
Image rhel7/etcd is being pulled to docker ...
[
    {
        "search": true,
        "hostname": "registry-1.docker.io",
        "name": "docker.io",
        "secure": true
    },
    {
        "search": true,
        "hostname": "registry.access.redhat.com",
        "name": "registry.access.redhat.com",
        "secure": true
    }
]

In 7.3.3, it seems atomic pull command searches/downloads image from "registry.access.redhat.com" registry prior to "registry-1.docker.io".

<snip>
Namespace(_class=<class 'Atomic.pull.Pull'>, assumeyes=False, debug=True, func='pull_image', image='rhel7/etcd', reg_type=None, storage=None)
Pulling registry.access.redhat.com/rhel7/etcd:latest ...
Executing: /usr/bin/skopeo --policy=/etc/containers/policy.json --debug copy --remove-signatures docker://registry.access.redhat.com/rhel7/etcd:latest docker-daemon:rhel7/etcd:latest
DEBU[0000] Using registries.d directory /etc/containers/registries.d for sigstore configuration 
DEBU[0000]  Using "default-docker" configuration        
DEBU[0000]  No signature storage configuration found for registry.access.redhat.com/rhel7/etcd:latest 
DEBU[0000] IsRunningImageAllowed for image docker:registry.access.redhat.com/rhel7/etcd:latest 
DEBU[0000]  Using default policy section                
DEBU[0000]  Requirement 0: allowed                      
DEBU[0000] Overall: allowed                             
DEBU[0000] GET https://registry.access.redhat.com/v2/   
DEBU[0000] Ping https://registry.access.redhat.com/v2/ err <nil> 
DEBU[0000] Ping https://registry.access.redhat.com/v2/ status 200 
DEBU[0000] GET https://registry.access.redhat.com/v2/rhel7/etcd/manifests/latest 
DEBU[0002] Will convert manifest from MIME type text/plain to application/vnd.docker.distribution.manifest.v2+json 
Copying blob sha256:154dc369ca0dfabd18ddeca63a8bced0dfaefaa0b2cd7cb6ec9513423d863652
DEBU[0002] Downloading rhel7/etcd/blobs/sha256:154dc369ca0dfabd18ddeca63a8bced0dfaefaa0b2cd7cb6ec9513423d863652 
DEBU[0002] GET https://registry.access.redhat.com/v2/rhel7/etcd/blobs/sha256:154dc369ca0dfabd18ddeca63a8bced0dfaefaa0b2cd7cb6ec9513423d863652 

</snip>

But the result is written "docker.io/rhel7/etcd" rather than "registry.access.redhat.com/rhel7/etcd/", it indeed confuses users.
Comment 3 Micah Abbott 2017-05-03 14:31:19 UTC 

*** This bug has been marked as a duplicate of bug 1437447 ***