Bug 1807234
| Summary: | mDNS plugin overwrites SRV records | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Nemec <bnemec> | |
| Component: | Networking | Assignee: | Antoni Segura Puimedon <asegurap> | |
| Networking sub component: | DNS | QA Contact: | Nataf Sharabi <nsharabi> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | medium | CC: | aos-bugs, bbennett, bnemec, dmace, vvoronko | |
| Version: | 4.4 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
Feature: Arbitrary hostnames for baremetal deployments.
Reason: Previously there was a dependency on having specific DNS names for master nodes. In order to eliminate that and allow deployers to use the hostnames they want, it was necessary to remove some name logic from the mdns plugin for coredns that forced the use of the old name scheme.
Result: Deployers can use any legal hostname they want for master nodes.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1809750 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-04 18:02:24 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: | 1809750 | |||
|
Description
Ben Nemec
2020-02-25 21:11:45 UTC
Is https://github.com/openshift/coredns/pull/25 a fix for this? It's not associated with the bz. Toni, can you handle this one please? Yes, 25 is the fix for this, although I guess I need a copy of the bug targeted against 4.5 as well. I'll get it cloned. Oh, there is no 4.5 version available on bz yet. That's why I hadn't opened anything for it. This one was to allow backporting since we'll need it in 4.4, which is why I didn't reference it in the 4.5 PR. Tested on: [kni@provisionhost-0-0 ~]$ oc version Client Version: 4.5.0-0.nightly-2020-05-20-053050 Server Version: 4.5.0-0.nightly-2020-05-20-053050 Kubernetes Version: v1.18.2 According to Ben Nemec: For the purposes of this bug, the main thing is to verify that the SRV record points at what you specify, not the hard-coded CNAME from coredns-mdns. Therefore, In order to verify: 1.login into master-0 from kni@provisionhost: ssh core@master-0 2.gain root access: sudo -s 3.copy the mdns configuration: cp /etc/mdns/config.hcl /etc/mdns/config1.hcl 4.change the host_name in /etc/mdns/config1.hcl to another name (for example:"master-0-0-0") 5.run: sudo crictl ps | grep mdns 6bee170740088 93b7d3550406466da140ce16bdbe635240993eaf6bd91df0bf8eec9bf3605ab2 12 minutes ago Running mdns-publisher 1 7e88cff203314 6.sudo crictl stop 6bee170740088 7.host -t SRV _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-2.ocp-edge-cluster-0.qe.lab.redhat.com. _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-1.ocp-edge-cluster-0.qe.lab.redhat.com. _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-0-0.ocp-edge-cluster-0.qe.lab.redhat.com. Note that the last record was updated to the new name in the config.hcl 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.5 image release 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:2409 |