Bug 1332541

Summary: Could not find registry API at https://registry.access.redhat.com
Product: Red Hat Satellite Reporter: Kim Borup <kborup>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bkearney, brubisch, casmith, cjenkins, dkaylor, dkypuros, erik-fedora, hajek, hippieben, inecas, jgiordan, jrfuller, jsherril, jswensso, loeffls1, mburgerh, mhrivnak, paji, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-30 11:55:39 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:

Description Kim Borup 2016-05-03 12:42:44 UTC
Description of problem:
When trying to sync the registry from Red Hat, the following error occurs Could not find registry API at https://registry.access.redhat.com which result in no sync of rhel registry

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


How reproducible:
All the time for more than one person.

Steps to Reproduce:
1. Create a product and then create a docker repo for https://registry.access.redhat.com with Docker upstream rhel
2. Sync the repo


Actual results:
Could not find registry API at https://registry.access.redhat.com

Expected results:
A sync of the Red Hat registry with all the tags. 

Additional info:
I can sync it fine from command line with docker pull. 

From within satellite i can sync fedora from docker.io 

 PulpCodedException(error_code=error_codes.DKR1008, registry=url)\nPulpCodedException: Could not find registry API at https://registry.access.redhat.com\n",

Comment 1 Ivan Necas 2016-05-17 09:26:43 UTC
*** Bug 1333671 has been marked as a duplicate of this bug. ***

Comment 6 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 7 Bryan Kearney 2016-07-26 15:29:08 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 14 Ivan Necas 2016-08-30 06:40:11 UTC
Going to `https://registry.access.redhat.com/v2/` returns 200, with response header “Docker-Distribution-API-Version” set to “registry/2.0”: it should now work with Satellite 6.2

Comment 15 Bryan Kearney 2016-08-30 11:55:39 UTC
Satellite 6.2 should be able to pull from the Red Hat registry which now suports v2. I am closing this as current release. If you are still seeing issues, please feel free to re-open with additional information.

Comment 16 David Kypuros 2016-11-18 15:38:29 UTC
I am also experiencing the same error "Could not fetch repository redhat-upstream from registry https://registry.access.redhat.com - NOT FOUND " from Satellite 6.2.