Bug 1788583

Summary:	Internal registry service DNS name not resolvable from IPv6 hosts
Product:	OpenShift Container Platform	Reporter:	Jon Schlueter <jschluet>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	DNS	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs
Version:	4.3.0
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ipv6
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1788591 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:23:07 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:
Bug Depends On:
Bug Blocks:	1788591

Description Jon Schlueter 2020-01-07 14:50:24 UTC

Description of problem:

Node Resolver is not able to pull correct DNS record for ipv6



Actual results:

Unable to specify the ipv6 IP for the service IP

Expected results:

able to specify ipv6 IP for the service IP

Additional info:

Patch cherry-pick to release-4.3 upstream
https://github.com/openshift/cluster-dns-operator/pull/152

Comment 2 Hongan Li 2020-03-24 07:52:13 UTC

verified with 4.4.0-0.nightly-2020-03-23-010639 and the issue has been fixed.

$ oc get svc -n openshift-image-registry
NAME                      TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)     AGE
image-registry            ClusterIP   fd02::bde    <none>        5000/TCP    10m

$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
fd02::bde image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver

Comment 4 errata-xmlrpc 2020-05-04 11:23:07 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581