Bug 1809750
Summary: | mDNS plugin overwrites SRV records | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Dan Mace <dmace> |
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: | aiyengar, aos-bugs, asegurap, bbennett, bnemec, dmace, hongli, vvoronko |
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1807234 | Environment: | |
Last Closed: | 2020-05-04 11:44:29 UTC | Type: | --- |
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: | 1807234 | ||
Bug Blocks: |
Description
Dan Mace
2020-03-03 19:40:36 UTC
Backport of https://github.com/openshift/coredns/pull/25 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-000") 5.Try to see if you can bound it into another ip address (just for test purposes) 6.find the mdns-publisher command: find / -name "mdns-publisher" | grep usr 7.open another session & ssh core@master-1 from kni@provisionhost 8.from master-1: watch -n 1 -d "nslookup master-0;nslookup <new name> " 9.from master-0: /var/lib/containers/storage/overlay/<con-id>/merged/usr/bin/mdns-publisher You can see in the log the published service is coordinated with the name you have given: [root@master-0 mdns]# /var/lib/containers/storage/overlay/a5b82797b04b8aa75e6beb80377a8ec48c3c72055c35f32cebacea04f1446916/merged/usr/bin/mdns-publisher --config _config.hcl INFO[0000] Publishing with settings collision_avoidance=hostname ip="fd2e:6f44:5dd8:c956::102" INFO[0000] Binding interface name=enp5s0 INFO[0000] Publishing service domain=local. hostname=etcd-0.local. name="ocp-edge-cluster Etcd-master-0" port=2380 ttl=3200 type=_etcd-server-ssl._tcp INFO[0000] Publishing service domain=local. hostname=master-000.local. name="ocp-edge-cluster Workstation-master-0" port=42424 ttl=3200 type=_workstation._tcp INFO[0000] Publishing service domain=local. hostname=etcd-0.local. name="ocp-edge-cluster EtcdWorkstation-master-0" port=42424 ttl=300 type=_workstation._tcp 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 |