Comment 19 for bug 1034161

Revision history for this message
Yang Zhenyu (yangzhenyu) wrote :

Hi Aaron
I add a define in the /iproute2/ip/ipnetns.c
#define __NR_setns 268

Then rebuilding iproute2, the problem has been solved.
Thank you

But, there is other error of dhcp When I create a network. And now the instance cannot obtain a IP address. The log:

 DEBUG [quantum.agent.linux.dhcp] Unable to access /opt/stack/data/dhcp/218d8883-7c1c-4332-8811-518d130fa419/pid

Stderr: 'cat: /proc/None/cmdline: No such file or directory\n'

Command: ['sudo', 'ip', 'netns', 'exec', '218d8883-7c1c-4332-8811-518d130fa419', 'ip', '-o', 'link', 'show', 'tap2afc920f-0f']
Exit code: 1
Stdout: ''
Stderr: 'seting the network namespace failed: Bad address\n'

Command: ['sudo', 'ip', 'link', 'set', 'tap2afc920f-0f', 'address', 'fa:16:3e:89:b1:61']
Exit code: 1
Stdout: ''
Stderr: 'Cannot find device "tap2afc920f-0f"\n'

#ovs-vsctl show

4d4b586f-1206-4eea-bd18-57011d490b16
    Bridge br-tun
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-int
        Port "tap2afc920f-0f"
            tag: 1
            Interface "tap2afc920f-0f"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}

I just hope the instance obtain a IP address from dhcp. Does it must use the network namespace?
Thanks.