Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1779989

Summary: OC Release Mirror ignores proxy configuration
Product: OpenShift Container Platform Reporter: Shivkumar Ople <sople>
Component: ocAssignee: Maciej Szulik <maszulik>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, jokerman, mfojtik
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: 2019-12-10 12:59:18 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 Shivkumar Ople 2019-12-05 07:58:16 UTC
Description of problem:

Call to oc adm release mirror runs into network timeout. Network logs show proxy configuration (HTTP_PROXY and HTTPS_PROXY environment variables) is ignored.


oc adm -a ${LOCAL_SECRET_JSON} release mirror --from=quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE} --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE} --loglevel=10


Log Output:
I1202 14:09:48.779130    2578 config.go:131] looking for config.json at /root/.docker/config.json
I1202 14:09:48.779590    2578 config.go:139] found valid config.json at /root/.docker/config.json
I1202 14:09:48.781286    2578 round_trippers.go:419] curl -k -v -XGET  'https://quay.io/v2/'
I1202 14:10:03.801833    2578 round_trippers.go:438] GET https://quay.io/v2/  in 15016 milliseconds
I1202 14:10:03.809105    2578 round_trippers.go:444] Response Headers:
I1202 14:10:03.833035    2578 workqueue.go:143] about to send work queue error: unable to connect to image repository quay.io/openshift-release-dev/ocp-release:4.2.8: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1202 14:10:03.836232    2578 workqueue.go:54] worker 0 stopping
F1202 14:10:03.841698    2578 helpers.go:114] error: unable to retrieve release image info: unable to connect to image repository quay.io/openshift-release-dev/ocp-release:4.2.8: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1202 14:10:03.843270    2578 workqueue.go:60] work queue exiting


Version-Release number of the following components:

OpenShift 4.2


How reproducible:
Always

Steps to Reproduce:
1. Install an actual "restricted network" Openshift 4.2 cluster without access to the internet

2. Run oc adm release mirror command mentioned in the above description.


Actual results:
Timeout error 

Expected results:

Additional info:

RHEL 7 Server used for preparation of OpenShift 4.2 disconnected bare metal installation.


Error:
~~~~~~~~~~~~~~~
I1202 14:10:03.833035    2578 workqueue.go:143] about to send work queue error: unable to connect to image repository quay.io/openshift-release-dev/ocp-release:4.2.8: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1202 14:10:03.836232    2578 workqueue.go:54] worker 0 stopping
F1202 14:10:03.841698    2578 helpers.go:114] error: unable to retrieve release image info: unable to connect to image repository quay.io/openshift-release-dev/ocp-release:4.2.8: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I1202 14:10:03.843270    2578 workqueue.go:60] work queue exiting
~~~~~~~~~~~~~~~~~

Comment 1 Abhinav Dahiya 2019-12-06 18:37:54 UTC
The release uses `oc image` code-flow internally to interact with container registries.. to moving to oc component for better triage.

Comment 2 Maciej Szulik 2019-12-10 12:59:18 UTC

*** This bug has been marked as a duplicate of bug 1769759 ***