Comment 2 for bug 1615390

Revision history for this message
Serguei Bezverkhi (sbezverk) wrote :

This happens in Kubernetes environment when neutron-l3-agent runs wihtin a docker container. I suspect the issue is more about ip netns returning RTNETLINK answers: Invalid argument, than the actual l3 agent issue.
Anything you can suggest for further troubleshooting?

ip netns
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
qdhcp-f32fdde6-bb99-4981-926b-a7df30f0a612
RTNETLINK answers: Invalid argument
qrouter-baa3335b-0013-42dd-856a-64a5c2557a01

This is taking on the host where l3 agent and dhcp containers are running..