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 1346619 - Unable to interact with a V1 registry
Summary: Unable to interact with a V1 registry
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-15 06:08 UTC by Alex Jia
Modified: 2016-08-19 22:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-19 22:12:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Jia 2016-06-15 06:08:34 UTC 
Description of problem:
atomic info w/ --remote option doesn't work and got error "Unable to interact with a V1 registry".

Version-Release number of selected component (if applicable):

[cloud-user@atomic-host-001 ~]$ cat /etc/redhat-release 
Red Hat Enterprise Linux Atomic Host release 7.2

[cloud-user@atomic-host-001 ~]$ sudo atomic host status
  TIMESTAMP (UTC)         VERSION     ID             OSNAME               REFSPEC                                                   
* 2016-06-13 17:33:11     7.2.5       5b82b4035f     rhel-atomic-host     rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard

[cloud-user@atomic-host-001 ~]$ rpm -q atomic docker python-docker-py
atomic-1.10.5-3.el7.x86_64
docker-1.10.3-40.el7.x86_64
python-docker-py-1.7.2-1.el7.noarch


How reproducible:
always

Steps to Reproduce:
1. $ sudo atomic info --remote registry.access.redhat.com/rhel7:latest


Actual results:

[cloud-user@atomic-host-001 ~]$ sudo atomic info --remote rhel7
Image Name: registry.access.redhat.com/rhel7:latest

Unable to interact with a V1 registry.

[cloud-user@atomic-host-001 ~]$ sudo atomic info --remote registry.access.redhat.com/rhel7
Image Name: registry.access.redhat.com/rhel7:latest

Unable to interact with a V1 registry.

[cloud-user@atomic-host-001 ~]$ sudo atomic info --remote registry.access.redhat.com/rhel7:latest
Image Name: registry.access.redhat.com/rhel7:latest

Unable to interact with a V1 registry.


Expected results:


Additional info:
Comment 2 Brent Baude 2016-06-15 15:18:52 UTC 
I'm not sure this is a bug on atomic.  It's a bug (or lack of function) for the RH registry.  The error message is very clear in stating it cannot interact with a V1 registry.
Comment 3 Alex Jia 2016-06-15 16:18:17 UTC 
(In reply to Brent Baude from comment #2)
> I'm not sure this is a bug on atomic.  It's a bug (or lack of function) for
> the RH registry.  The error message is very clear in stating it cannot
> interact with a V1 registry.

Brent, yes, but I think it may be not a RH registry issue, because it works well w/ atomic-1.9-4.gitff44c6a.el7.x86_64 and docker-1.9.1-40.el7.x86_64, however, it doesn't work w/ atomic-1.10.5-3.el7.x86_64 and docker-1.10.3-40.el7.x86_64.

# rpm -q docker atomic
docker-1.9.1-40.el7.x86_64
atomic-1.9-4.gitff44c6a.el7.x86_64

# atomic info --remote registry.access.redhat.com/rhel7:latest
Vendor: Red Hat, Inc.
Name: rhel7/rhel
Build_Host: rcm-img03.build.eng.bos.redhat.com
Version: 7.2
Architecture: x86_64
Release: 61
BZComponent: rhel-server-docker
Authoritative_Registry: registry.access.redhat.com
Comment 4 Alex Jia 2016-06-15 16:49:27 UTC 
Brent, the same issue to atomic pull command, but it works well for atomic update, does atomic pull only support pull image from RH atomic registry now? or still support both RH docker registry and atomic registry?
Comment 5 Daniel Walsh 2016-06-15 18:31:41 UTC 
I think the atomic pull issues are different.

Theoretically 
atomic pull docker:rhel7

Should work.  Currently the command is defaulted to ostree.
Comment 6 Brent Baude 2016-06-16 16:14:39 UTC 
Whatever pull issues you are seeing are different.

The use of --remote with atomic commands will then call skopeo.  Skopeo only works with v2 registries.  Because the RH registry is only V1, it will fail for remote inspection.
Comment 7 Daniel Walsh 2016-08-19 22:12:18 UTC 
This is working as designed.
Note You need to log in before you can comment on or make changes to this bug.