A presentation given at the Manchester OpenStack Meetup, talking through some of the odd things we've hit up against in our time as a public OpenStack operator using Neuton with OpenvSwitch.
8. Common problems - typical user complaints
• VM can't obtain an IP address
• Can't ping / connect to my VM
• Intermi9ent connec:vity
9. Weirdness #1 - orphaned namespaces
• Default (on Ubuntu) is not to delete namespaces at all (!)
• Bug in iproute2 package
• h=ps://bugs.launchpad.net/neutron/+bug/1052535
• Misconfigured sudo rules meant that network namespaces
weren't being deleted
• Mismatch between interfaces configured in a namespace and
what Neutron expects
10. Finding out what's supposed to be where
for netnode in osnet{0..4} ; do
echo $netnode
for router in $(ssh $netnode 'ip netns list | grep qrouter | cut -d - -f 2-20') ; do
neutron router-show $router | grep -i unable
done
done
Then delete each invalid namespace and associated OVS port.
• Pro%p: Don't run neutron-ovs-cleanup!
11. Weirdness #2 - duplicate segmenta4on ID
• Customer support ,cket with instances unable to obtain an IP via
DHCP
• Some serious digging required...
12. Tracing packet flows
• tcpdump on compute node and in network namespaces
• Packets not always arriving where you'd expect
• Have to look at OpenFlow rules
17. Weirdness #3 - duplicate routers
• Intermi)ent connec-vity issues groan
• No DVR or L3-HA enabled
• Routers scheduled and created twice on two network nodes
• Same network configura-on in each namespace
19. How to approach troubleshoo0ng
Troubleshoo*ng checklist
• UUIDs for instance, loca2on, MAC address
• UUIDs for network, subnet, router
• Network node hos2ng L2 and L3 agents