- deleting the qdhcp-xxx and letting neutron_dhcp re-create it doesn't make it batter.
- creating the qdhcp-xxx by hand and letting neutron_dhcp do its stuff doesn't help either
But, deleting the qdhcp-xx and letting neutron_dhcp re-create it allows to get the commands, more or less.
In order:
(3, 'neutron.privileged.agent.linux.ip_lib.create_netns', (u'qdhcp-3c92f030-45b4-4927-a83f-b2141a18877f',), {})
So.... Some more stuff:
- deleting the qdhcp-xxx and letting neutron_dhcp re-create it doesn't make it batter.
- creating the qdhcp-xxx by hand and letting neutron_dhcp do its stuff doesn't help either
But, deleting the qdhcp-xx and letting neutron_dhcp re-create it allows to get the commands, more or less.
In order: privileged. agent.linux. ip_lib. create_ netns', (u'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f',), {})
(3, 'neutron.
shell is: ip netns add qdhcp-xxx
['ip', 'netns', 'exec', 'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f', 'sysctl', '-w', 'net.ipv4. conf.all. promote_ secondaries= 1']
shell is the same, without quotes, of course
(3, 'neutron. privileged. agent.linux. ip_lib. set_link_ attribute' , ('lo', u'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f'), {'state': 'up'})
shell is: ip link set lo up netns qdhcp-3c92f030- 45b4-4927- a83f-b2141a1887 7f
And there, we have a first failure:
RTNETLINK answers: Invalid argument
Also reported from the log itself:
(4, [{'header': {'pid': 24464, 'length': 36, 'flags': 0, 'error': None, 'type': 2, 'sequence_number': 255}, 'event': 'NLMSG_ERROR'}])
['ip', 'netns', 'exec', 'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f', 'sysctl', '-w', 'net.ipv6. conf.default. accept_ ra=0']
shell is the same, without quotes.
(3, 'neutron. privileged. agent.linux. ip_lib. get_link_ attributes' , (u'tape2d00740-20', u'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f')
shell is: (don't know, there isn't ip link get <device> netns qdhcp-xxx)
We get: Network interface tape2d00740-20 not found in namespace qdhcp-3c92f030- 45b4-4927- a83f-b2141a1887 7f.
(3, 'neutron. privileged. agent.linux. ip_lib. set_link_ attribute' , (u'tape2d00740-20', None), {'address': u'fa:16: 3e:07:55: 2c'})
shell is: ip link set tape2d00740-20 address fa:16:3e:07:55:2c
there again, failure:
(4, [{'header': {'pid': 4294961794, 'length': 36, 'flags': 0, 'error': None, 'type': 2, 'sequence_number': 255}, 'event': 'NLMSG_ERROR'}])
and from the shell: Cannot find device "tape2d00740-20"
(3, 'neutron. privileged. agent.linux. ip_lib. set_link_ attribute' , (u'tape2d00740-20', None), {'net_ns_fd': u'qdhcp- 3c92f030- 45b4-4927- a83f-b2141a1887 7f'})
shell is: ??
failure: (4, [{'header': {'pid': 4294961791, 'length': 36, 'flags': 0, 'error': None, 'type': 2, 'sequence_number': 255}, 'event': 'NLMSG_ERROR'}])
and so on.
So apparently there's an issue linking OVS managed interfaces with netns.