Description of problem:
Cluster Logging and Elasticsearch Operators cannot be deployed on IPv6 AWS environment. OperatorSources cannot be configured because the endpoints use quay.io which is not IPv6 enabled:
oc -n openshift-marketplace get OperatorSource
NAME TYPE ENDPOINT REGISTRY DISPLAYNAME PUBLISHER STATUS MESSAGE AGE
certified-operators appregistry https://quay.io/cnr certified-operators Certified Operators Red Hat Configuring Get https://quay.io/cnr/api/v1/packages?namespace=certified-operators: dial tcp 34.231.142.215:443: connect: network is unreachable 24h
community-operators appregistry https://quay.io/cnr community-operators Community Operators Red Hat Configuring Get https://quay.io/cnr/api/v1/packages?namespace=community-operators: dial tcp 107.21.16.71:443: connect: network is unreachable 24h
redhat-operators appregistry https://quay.io/cnr redhat-operators Red Hat Operators Red Hat Configuring Get https://quay.io/cnr/api/v1/packages?namespace=redhat-operators: dial tcp 34.195.11.195:443: connect: network is unreachable 24h
Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-01-06-101556-ipv6.1
How reproducible:
100%
Steps to Reproduce:
1. Deploy an IPv6 cluster on AWS
2. Check oc -n openshift-marketplace get OperatorSource
Actual results:
OperatorSource are stuck in 'Configuring' status because quay.io cannot be reached as it is not IPv6 enabled. This blocks installing the cluster Logging and Elasticsearch Operators according to:
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.2/html/logging/cluster-logging-deploying
Expected results:
Have the ability to install the cluster Logging and Elasticsearch Operators on an IPv6 enabled environment.
Additional info:
Comment 1Alexander Chuzhoy
2020-01-07 18:49:27 UTC
If someone can clarify exactly which pods require IPv4 access to quay, we have a workaround in our AWS IPv6 clusters to grant IPv4 access to select pods that need it to function.
The pods in question are the catalog pods in `openshift-marketplace` namespace (they have names like `redhat-operators-*`).
Since there is a workaround that doesn't involve quay supporting ipv6, I have moved this bug back to OLM for verification in 4.4, so that we can backport the linked PR to 4.3