Bug 2021026

Summary: Can't pull the image through private registry in OCP 4.8 - "rpc error: code = Unknown desc = error pinging docker registry registry.access.redhat.com"
Product: OpenShift Container Platform Reporter: kwwong
Component: NodeAssignee: Qi Wang <qiwan>
Node sub component: CRI-O QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED WORKSFORME Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, dornelas, miabbott, qiwan, wewang
Version: 4.8   
Target Milestone: ---   
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: 2022-01-26 20:27:21 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 kwwong 2021-11-08 06:28:59 UTC
Description of problem: 
The customer failed to pull the image from their private registry in OCP 4.8, which was working on OCP 4.7, the customer is working in a disconnected environment.

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


How reproducible:
customer updated the cluster from 4.7 to 4.8, and lose the capability to pull images, they updated a second cluster, and the same issue persisted.

Steps to Reproduce:
1. mirror openshift3/oauth-proxy from https://registry.access.redhat.com to a private docker registry
2. change the registry location in /etc/containers/registries.conf
3. pull image from private registry

Actual results: Openshift is ignoring the mirror setting in the /etc/containers/registries.conf 

Expected results: access the image from own registry


Additional info:

Comment 11 Qi Wang 2021-12-20 21:07:29 UTC
(In reply to kwwong from comment #8)
> 
> [[registry]]
>   prefix = ""
>   location = "registry.redhat.io"
>   mirror-by-digest-only = false
> 
>   [[registry.mirror]]
>     location = "dockerhub.rnd.amadeus.net:xxxx"
> 

Hi, the customer wants to mirror registry.access.redhat.com to their private mirror registry, but the above 
registry.conf is mirroring "registry.redhat.io" to the mirror registry.

From the log, the image pull used "registry.access.redhat.com"  that doesn't match the source registry "registry.redhat.io" in the registry.conf so the mirror registry hasn't been used. A workaround is replacing the above location = "registry.redhat.io" with location = "registry.access.redhat.com".

Comment 17 kwwong 2022-01-23 23:46:03 UTC
Hi Qi, 

Thank you so much for your help, I am delighted to know this bug has been addressed. You may now close this ticket.


Kind regards,

Jaime