search

andrewdmcleod / magpie-layer

testing
Apache License 2.0
0 stars 12 forks source link

DNS Forward dig command malformed when DNS returns multiple hostsnames #5

Closed jogeo closed 5 years ago

jogeo commented 6 years ago

Two units of Magpie were deployed with MAAS as the substrate.

magpie/8* blocked idle 1 10.246.65.74 icmp ok, local hostname ok, fwd dns failed: ['9'], iperf leader, mtu: 1500 magpie/9 blocked idle 2 10.246.65.61 icmp ok, local hostname ok, fwd dns failed: ['8'], net mtu failed, mismatch: 8988 packet vs 1500 on iface br-eth0, 989 mbit/s

The fwd dns failure is caused by a malformed shell command, as can be seen in the unit log: 2018-06-06 22:23:26 INFO juju-log magpie:219: Forward lookup for hostname: 67.64-26.36.168.192.in-addr.arpa. bond0.2736.pangoro.maas., node: magpie/9, unit_id: 9 2018-06-06 22:23:26 DEBUG worker.uniter.jujuc server.go:181 running hook tool "juju-log" 2018-06-06 22:23:26 DEBUG juju-log magpie:219: DNS Forward command: /usr/bin/dig 67.64-26.36.168.192.in-addr.arpa. bond0.2736.pangoro.maas. +short +tries=1 +time=3 2018-06-06 22:23:26 DEBUG magpie-relation-changed /bin/sh: 2: bond0.2736.pangoro.maas.: not found

This appears to be due to multiple results returned from reverse DNS: $ dig -x 192.168.36.67 +short +tries=1 +time=3 67.64-26.36.168.192.in-addr.arpa. bond0.2736.pangoro.maas.

Please see the attached log and captured configuration details magpie_forward_lookup_failure.tar.gz