Bug 1900729 - None of Red Hat container registries are available via IPv6
Summary: None of Red Hat container registries are available via IPv6
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-23 15:32 UTC by rovandep
Modified: 2020-11-24 11:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-23 19:27:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rovandep 2020-11-23 15:32:33 UTC
Description of problem:

None of the Red Hat container registries:
- registry.redhat.io
- quay.io
This is requirement when having a fully IPv6 based deployment of OCP and/or for hosts used to build container on within an IPv6 network.

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


How reproducible:
Always

Steps to Reproduce:
1. have a IPv6 only system like a host on which image would be build 
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:b9:9b:57 brd ff:ff:ff:ff:ff:ff
    inet6 2a01:***:**:**::***/128 scope global dynamic noprefixroute 
       valid_lft 3020sec preferred_lft 3020sec

2. proper dns resolutions
# nslookup google.com
Server:		2a01:***:**:**::***
Address:	2a01:***:**:**::***#53

Non-authoritative answer:
Name:	google.com
Address: 172.217.22.174
Name:	google.com
Address: 2a00:1450:400f:807::200e

3. pull a container from quay.io:
# podman pull quay.io/coreos/etcd
Trying to pull quay.io/coreos/etcd...
  Get https://quay.io/v2/: dial tcp 52.201.153.168:443: connect: network is unreachable
Error: error pulling image "quay.io/coreos/etcd": unable to pull quay.io/coreos/etcd: unable to pull image: Error initializing source docker://quay.io/coreos/etcd:latest: error pinging docker registry quay.io: Get https://quay.io/v2/: dial tcp 52.201.153.168:443: connect: network is unreachable

4. pull a container from registry.access.redhat.com
# podman pull registry.access.redhat.com/ubi8-minimal
Trying to pull registry.access.redhat.com/ubi8-minimal...
  Get https://registry.access.redhat.com/v2/: dial tcp 2.16.187.64:443: connect: network is unreachable
Error: error pulling image "registry.access.redhat.com/ubi8-minimal": unable to pull registry.access.redhat.com/ubi8-minimal: unable to pull image: Error initializing source docker://registry.access.redhat.com/ubi8-minimal:latest: error pinging docker registry registry.access.redhat.com: Get https://registry.access.redhat.com/v2/: dial tcp 2.16.187.64:443: connect: network is unreachable


5. pull a container from registry.redhat.io
# podman login registry.redhat.io
Username: rhn-support-
Password: 
Error: error authenticating creds for "registry.redhat.io": error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp 23.43.115.178:443: connect: network is unreachable
[root@etcd-cluster ~]# podman pull registry.redhat.io/ubi8-minimal
Trying to pull registry.redhat.io/ubi8-minimal...
  Get https://registry.redhat.io/v2/: dial tcp 23.43.115.178:443: connect: network is unreachable
Error: error pulling image "registry.redhat.io/ubi8-minimal": unable to pull registry.redhat.io/ubi8-minimal: unable to pull image: Error initializing source docker://registry.redhat.io/ubi8-minimal:latest: error pinging docker registry registry.redhat.io: Get https://registry.redhat.io/v2/: dial tcp 23.43.115.178:443: connect: network is unreachable

Actual results:
Failure to resolve and connect


Expected results:
Being able to login and pull images from Red Hat registry services in IPv6


Additional info:

Comment 2 Oleg Bulatov 2020-11-23 19:27:06 UTC
I contacted people from quay.io and registry.redhat.io. Now they both have stories to support IPv6.

Closing this BZ as it's not about OpenShift Image Registry.

Comment 3 rovandep 2020-11-23 20:40:16 UTC
Could you share the story references?
Also, for future needs, if not related to OpenShift Image Registry, which I understand, what's the correct category to refer to or ticketing tools for SaaS based registries?

Thanks.

Comment 4 Oleg Bulatov 2020-11-24 11:32:27 UTC
Here is the reference for Quay: https://issues.redhat.com/browse/PROJQUAY-131


Note You need to log in before you can comment on or make changes to this bug.