dns not working and dhcp namespace has two tap interfaces
Hi,
A problem appeared (I guess) when I tried to add another external network to add one more floating ip range, and then deleted it.
Now, dns does not reply in my vms (for some tenants it does) What i found out is that in my qdhcp namespace i got two tap interfaces,
ip netns exec qdhcp-43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea ifconfig
...
tap2e4ca852-ea: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.33.3 netmask 255.255.255.0 broadcast 192.168.33.255
inet6 fe80::f816:3eff:fe04:1659 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:04:16:59 txqueuelen 0 (Ethernet)
RX packets 148263 bytes 20487809 (19.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 25210 bytes 3433433 (3.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tapfaa2eb73-9f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.33.17 netmask 255.255.255.0 broadcast 192.168.33.255
inet6 fe80::f816:3eff:fed0:e2c prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:d0:0e:2c txqueuelen 0 (Ethernet)
RX packets 429 bytes 40643 (39.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 118 bytes 10171 (9.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Moreover, when i do nslookup from a VM i get packets only on one tap interface: tap2e4ca852-ea
In VM's resov.conf, i have two nameservers: 192.168.33.3 and 192.168.33.17 but traffic from both of them go to one tap interface....
however, in my process list i got
nobody 2236 0.0 0.0 15528 756 ? S 22:38 0:00 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=tapfaa2eb73-9f --except-interface=lo --pid-file=/var/lib/neutron/dhcp/43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea/host --addn-hosts=/var/lib/neutron/dhcp/43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea/opts --leasefile-ro --dhcp-range=set:tag0,192.168.33.0,static,86400s --dhcp-lease-max=256 --conf-file= --server=10.21.0.4 --domain=uni.lux
as you see, --interface=tapfaa2eb73-9f
is the interface where packets do not simply go.
I also went to /var/lib/neutron/dhcp/43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea
and tried to change
the content of interface
file from tapfaa2eb73-9f
to tap2e4ca852-ea
but after restarting neutron-dhcp-agent,
the value of that file was restored.
Question: how do I change the tap interface to bind dnsmasq? (or maybe how to make traffic go to that interface dnsmasq is bond to)?
I have an RDO installation IceHouse on Fedora 20; VLAN for tenants.
Thanks for any hints!
After darragh-oreilly's suggestions.
I removed port that started with faa2eb73-9f
neutron port-delete faa2eb73-9f8f-4e66-a50a-846e8f283636
restarted all neutron services on controller/network node; also restarted openvswitch
What changed?
in VM's resolv.conf i get now 1 nameserver nameserver 192.168.33.21
TAP interfaces: new one appeared; old stayed
ip netns exec qdhcp-43bf6a7d-8b0a-4be2-90dc-4f75de1ee4ea ifconfig
tap05de60a7-45: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.33.21 ...
I'm not sure how you got to this situation, but it seems like a bug that this network has two ports for this host. Do
neutron port-list
to get the full port-ids andneutron port-show $PORT_ID
on each port. Maybe deleting the port that starts with faa2eb73-9f and restarting the agent will do it.I deleted a port that started with faa2eb.. and restarted dhcp-agent. Now i have 3 tap interfaces in the same namespace. The faa2eb is still there...
who should kill these tap interfaces when port is deleted?
so you deleted it with
neutron port-delete $PORT_ID
? Can you postneutron port-show $PORT_ID
for the 3 ports - as admin so the port:bindings etc are shown?Thanks for helping out! I updated it in the question (now it's long...) Should I also delete the 1st (oldest) port 2e4ca852-eaca-45f6-ad2a-06f6fa6f8601?