Bug 1572302
| Summary: | DKR1008: Could not find registry API at https://gcr.io | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Satellite Program <pm-sat> | ||||
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3.0 | CC: | adprice, ahuchcha, aleks, amdas, bmbouter, daviddavis, djoo, dkliban, ggainey, ipanova, mhrivnak, mmccune, paji, pcreech, rchan, ttereshc | ||||
| Target Milestone: | 6.4.0 | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1555165 | Environment: | |||||
| Last Closed: | 2018-10-16 19:05:18 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Comment 2
pulp-infra@redhat.com
2018-04-26 16:32:04 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug. *** Bug 1564830 has been marked as a duplicate of this bug. *** Failed QA in Satellite 6.4 snap 7 Created new product and repo to test this. created three repositories: a new project hosted on my google cloud account, using my auth creds. an existing google project google_containers/kube-controller-manager-amd64, with no auth creds. an existing google project google_containers/kube-controller-manager-amd64, with my auth creds. The first and third repo syns failed with the initial bug error: Could not find registry API at https://gcr.io/ The second repo failed with: Could not fetch repository google_containers/kube-controller-manager-amd64 from registry https://gcr.io/ - Unauthorized or Not Found Additionally, it looks like the linked code changes are not in the files included in this version. Requesting needsinfo from upstream developer ipanova because the 'FailedQA' flag is set. snap 7 contains pulp-server-2.16.0-2.el7sat.noarch.rpm. this bugfix will go into 2.16.2. Beta will be available June 19. Requesting needsinfo from upstream developer ipanova because the 'FailedQA' flag is set. The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. Verified in Satellite 6.4 Snap 12. Both unauthenticated and authenticated sync of the repo, mentioned in comment #5, worked without issues. See attached screenshot for verification. Created attachment 1459799 [details]
verification screenshot
Do you plan to back-port the fix to 6.3.x? As we have a customer which have the same problem with quay.io as describe in #1564830 . There is also a customer case behind this request 02166069 @Aleks, See the cloned bug to find out which build of 6.3.z this is fixed in. @Robin, I don't see there any fixed version on a `git checkout grc-sat` which could not be the solution for the product.
In the logs are this messages
```
Aug 21 16:26:54 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (1): quay.io
Aug 21 16:26:54 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (2): quay.io
Aug 21 16:26:56 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (3): quay.io
Aug 21 16:27:00 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (4): quay.io
Aug 21 16:27:08 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (5): quay.io
Aug 21 16:27:24 <SERVER> pulp: [ID - daemon.info] requests.packages.urllib3.connectionpool:INFO: [dbf34b91] Starting new HTTPS connection (6): quay.io
Aug 21 16:27:24 <SERVER> pulp: [ID - daemon.err] nectar.downloaders.threaded:ERROR: [dbf34b91] Skipping requests to quay.io due to repeated connection failures: HTTPSConnectionPool(host='quay.io', port=443): Max retries exceeded with url: /v2/ (Caused by ProtocolError('Connection aborted.', gaierror(-2, 'Name or service not known')))
Aug 21 16:27:24 <SERVER> pulp: [ID - daemon.info] pulp.server.async.tasks:INFO: [dbf34b91] Task failed : [dbf34b91-ea1f-4034-9dbd-367e7ea7d27f] : Could not find registry API at https://quay.io/
```
@Aleks - I was looking at notes in "Devel Whiteboard:" field of "Clone of" bug: https://bugzilla.redhat.com/show_bug.cgi?id=1555165 @Robin. thanks. looks like in https://bugzilla.redhat.com/show_bug.cgi?id=1333595 is a fix for 6.3.3 we will wait for the new version 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/RHSA-2018:2927 |