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

Bug 1810860

Summary: [IPv6]Cannot configure to use mirrors for build in IPv6 Cluster
Product: OpenShift Container Platform Reporter: Wenjing Zheng <wzheng>
Component: BuildAssignee: Gabe Montero <gmontero>
Status: CLOSED NEXTRELEASE QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.zCC: aos-bugs, gmontero, wzheng
Target Milestone: ---Keywords: Reopened
Target Release: 4.3.z   
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: 2020-03-10 11:35:27 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:
Attachments:
Description Flags
image registry log none

Description Wenjing Zheng 2020-03-06 03:53:30 UTC 
Created attachment 1667981 [details]
image registry log

Description of problem:
Cannot configure to use mirrors for build in IPv6 Cluster:
$ oc logs -f build/test-1
Replaced Dockerfile FROM image docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9
Caching blobs under "/var/cache/blobs".

Pulling image docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9 ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
Warning: Pull failed, retrying in 5s ...
error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9" as "docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9": Error initializing source docker://nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9: error pinging docker registry registry-1.docker.io: Get https://registry-1.docker.io/v2/: dial tcp 100.24.246.89:443: connect: network is unreachable 

# oc get pods
test-1-build                     0/1     Error              0          57s    fd01::3:a8c3:c1ff:fe00:2f   master-2.ocp-edge-cluster.qe.lab.redhat.com   <none>           <none>


Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-03-04-165955

How reproducible:
Always

Steps to Reproduce:
1. Mirror image
# oc image mirror docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9 registry.ocp-edge-cluster.qe.lab.redhat.com:5000/openshift/centos7-s2i-nodejs -a all-secret.txt
2.Create an ICSP:
apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: wzhengbuild
spec:
  repositoryDigestMirrors:
  - mirrors:
    - registry.ocp-edge-cluster.qe.lab.redhat.com:5000/openshift/centos7-s2i-nodejs
    source: docker.io/nodeshift/centos7-s2i-nodejs
3.$ oc create secret generic ipv6secret --from-file=.dockerconfigjson=./mirror-ipv6-registry.txt --type=kubernetes.io/dockerconfigjson
4.$oc secrets link builder ipv6secret
5.$oc new-build -D 'FROM docker.io/nodeshift/centos7-s2i-nodejs@sha256:eea192da5dc21ddfbfbc1a1947ecb3c73e074e2d9516e5bed7ce66015464cce9' --strategy=docker --to=test

Actual results:
Cannot pull mirror image.

Expected results:
Build should be succeed.

Additional info:
Note: registry.ocp-edge-cluster.qe.lab.redhat.com:5000 is an IPv6 registry.
Comment 1 Wenjing Zheng 2020-03-06 03:53:57 UTC 
*** Bug 1810497 has been marked as a duplicate of this bug. ***