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 1455575 - atomic install registry.access.redhat.com/jboss-eap-7-tech-preview/eap70 fails with 'unknown: Not Found'
Summary: atomic install registry.access.redhat.com/jboss-eap-7-tech-preview/eap70 fail...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: skopeo
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2017-05-25 13:50 UTC by Igor Netkachev
Modified: 2020-06-11 13:53 UTC (History)
7 users (show)

Fixed In Version: skopeo-1:0.1.23-1.git1bbd87f
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-05 10:37:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2601 0 normal SHIPPED_LIVE skopeo bug fix update 2017-09-05 14:33:11 UTC

Description Igor Netkachev 2017-05-25 13:50:21 UTC 
Description of problem:
On Atomic host, after making sure that all required subscriptions and entitlements are in place, command

# atomic install registry.access.redhat.com/jboss-eap-7-tech-preview/eap70 

fails with

unknown: Not Found

At the same time, 'docker pull registry.access.redhat.com/jboss-eap-7-tech-preview/eap70' works without any issues.  Other Tech Preview images do not have this problem.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Atomic Host release 7.3
Linux unused 3.10.0-514.16.1.el7.x86_64 #1 SMP Fri Mar 10 13:12:32 EST 2017 x86_64 x86_64 x86_64 GNU/Linux
atomic-1.16.5-1.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Install Atomic host
2. Subscribe and attach all entitlements required for Tech Preview images
3. Run 'atomic install registry.access.redhat.com/jboss-eap-7-tech-preview/eap70'

Actual results:
error:
unknown: Not Found

Expected results:
image successfully pulled from registry and installed


Additional info:

It seems to be failing on "GET https://registry.access.redhat.com/v2/jboss-eap-7-tech-preview/eap70/manifests/latest":

# /usr/bin/skopeo --debug --tls-verify=false  inspect docker://registry.access.redhat.com/jboss-eap-7-tech-preview/eap70
WARN[0000] '--tls-verify' is deprecated, please set this on the specific subcommand 
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/jboss-eap-7-tech-preview/eap70:latest 
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/jboss-eap-7-tech-preview/eap70/manifests/latest 
FATA[0001] unknown: Not Found   


--
Kind Regards,
Igor Netkachev
Technical Support Engineer
Red Hat Global Support Services
Comment 1 Brent Baude 2017-05-25 14:03:14 UTC 
i get the same response when trying to pull this with docker.  This looks like a registry issue ?
Comment 2 Brent Baude 2017-05-25 14:47:07 UTC 
Ok, so once registered, the proper cert is used by docker to pull it ... looking now at the case where atomic/skopeo tries to pull it.
Comment 3 Miloslav Trmač 2017-05-25 15:01:31 UTC 
Besides everything else (this is _not_ the core issue), the weird error message is caused by the server using the error reporting interface incorrectly:

> HTTP/1.1 404 NOT FOUND
> Connection: close
> Content-Length: 53
> Content-Type: application/json
> Date: Thu, 25 May 2017 14:44:16 GMT
> Server: Apache
> 
> {"errors": [{"code": "404", "message": "Not Found"}]}

The "code" value is supposed to be one of specific registered strings (github.com/docker/distribution/registry/api/errcode.Register), in this case perhaps NAME_UNKNOWN or MANIFEST_UNKNOWN (really, it would be more user friendly not to pretend that the image does not exist but to explicitly say “authorization denied” or something like that, but that’s another separate issue). Using "code": "404" causes the error code decoder to fall back to that "unknown error" string.
Comment 14 Alex Jia 2017-08-17 06:13:08 UTC 
This issue has been verified in skopeo-0.1.23-1.git1bbd87f.el7.x86_64.
Comment 16 errata-xmlrpc 2017-09-05 10:37:48 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, 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-2017:2601
Note You need to log in before you can comment on or make changes to this bug.