Description of problem:
In IPv6 bare metal deployment log in to Kibana dashboard fails with 500 Internal error Get https://fd02::1/.well-known/oauth-authorization-server: dial tcp: lookup fd02:: no such host
Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-03-09-172027 with elasticsearch-operator.4.3.1-202002032140
Steps to Reproduce:
1. Deploy bare metal IPI setup with IPv6 control plane
2. Follow deployment procedure @ https://access.redhat.com/documentation/en-us/openshift_container_platform/4.3/html-single/logging/index#cluster-logging-deploying
3. Reach the Kibana route
500 Internal Error
Get https://fd02::1/.well-known/oauth-authorization-server: dial tcp: lookup fd02:: no such host
IPv6 address should be wrapped in square brackets
The same issue was solved for Grafana in BZ#1798195
Please provide the pod yaml for Kibana. The fix referenced in BZ#1798195 was against the oauth-proxy which is the same proxy that fronts Kibana. This would be resolvable by using the same proxy image.
Following the errata from the referenced bug would indicate oauth-proxy-container-v4.3.5-202003020549 image would resolve this issue.
Not sure what happened but I tried reproducing the issue with a newer build and I couldn't. This is the version where it works fine - 4.3.0-0.nightly-2020-03-12-145437 with elasticsearch-operator.4.3.5-202003020549 and clusterlogging.4.3.5-202003020549.