Bug 1820785
| Summary: | baremetal: *.apps DNS record broken on ipv6 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Nemec <bnemec> | |
| Component: | Machine Config Operator | Assignee: | Ben Nemec <bnemec> | |
| Status: | CLOSED ERRATA | QA Contact: | Victor Voronkov <vvoronko> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.5 | CC: | amurdaca, asegurap, augol, eweiss, kgarriso, smilner, vvoronko | |
| Target Milestone: | --- | |||
| Target Release: | 4.6.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: Some DNS records were hard-coded for ipv4
Consequence: Some records were not served correctly in ipv6 environments, which might necessitate creating those records in an external DNS server.
Fix: DNS records are now populated correctly based on the ip version in use.
Result: Internal records are now served correctly in both ipv4 and ipv6.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1851541 (view as bug list) | Environment: | ||
| Last Closed: | 2020-10-27 15:57:43 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: | 1851541 | |||
|
Description
Ben Nemec
2020-04-03 21:07:12 UTC
So I just need to run an nslookup on an IPV6 BM environment? Tested on IPV6 4.5 env on titan37. Pulled the DNS_VIP and ingress and tried nslookup and dig....still results in NXDOMAIN. The fix for this has not merged yet. Considering adding an nslookup to test this, after the fix is merged. The fix didn't merge until after 4.6 opened, so this isn't actually fixed on 4.5 yet. It will need to be backported. (In reply to Ben Nemec from comment #12) > The fix didn't merge until after 4.6 opened, so this isn't actually fixed on > 4.5 yet. It will need to be backported. 4.5 took off, I think you have to target a z stream of 4.5 by cloning and this goes to 4.6 Okay, 4.6 should be good to go. I've cloned this to 4.5 so we'll proceed with that one. [kni@provisionhost-0-0 ~]$ oc version
Client Version: 4.6.0-0.nightly-2020-07-07-233934
Server Version: 4.6.0-0.nightly-2020-07-07-233934
Kubernetes Version: v1.18.3+a377312
[kni@provisionhost-0-0 ~]$ cat install-config.yaml | grep ingressVIP
ingressVIP: fd2e:6f44:5dd8::10
IPv6 resolving working:
[core@master-0-0 ~]$ host 123.apps.ocp-edge-cluster-0.qe.lab.redhat.com
123.apps.ocp-edge-cluster-0.qe.lab.redhat.com has IPv6 address fd2e:6f44:5dd8::10
=== no errors on master coreDns log with A instead of AAAA record
[core@master-0-0 ~]$ sudo cat /var/log/containers/coredns-master-0-0.ocp-edge-cluster-0.qe.lab.redhat.com_openshift-kni-infra_coredns-8c7c47952056158eabf43f1a6e9663cc7ce4b749e94d96792cb957b6f088b804.log | grep -v INFO
2020-07-09T09:12:45.947690599+00:00 stdout F .:53
2020-07-09T09:12:45.947980925+00:00 stdout F CoreDNS-1.6.6
2020-07-09T09:12:45.947980925+00:00 stdout F linux/amd64, go1.14.4,
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 (OpenShift Container Platform 4.6 GA Images), 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:4196 |