I have exactly the same version of iproute on centos6.5, and I can do this:
[root@vagrant-centos65 vagrant]# ip -V
ip utility, iproute2-ss091226
[root@vagrant-centos65 vagrant]# ip netns add foo
[root@vagrant-centos65 vagrant]# ip netns list
foo
[root@vagrant-centos65 vagrant]# ip netns del foo
[root@vagrant-centos65 vagrant]# ip netns list
[root@vagrant-centos65 vagrant]# uname -a
Linux vagrant-centos65.vagrantup.com 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Are you sure that the node in which dhcp agent is running has the same version of iproute?
Another possibility would be dhcp agent is executing a different binary (if multiple versions are installed on different paths)?
Hi Patrick,
I have exactly the same version of iproute on centos6.5, and I can do this:
[root@vagrant- centos65 vagrant]# ip -V centos65 vagrant]# ip netns add foo centos65 vagrant]# ip netns list centos65 vagrant]# ip netns del foo centos65 vagrant]# ip netns list centos65 vagrant]# uname -a centos65. vagrantup. com 2.6.32- 431.3.1. el6.x86_ 64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
ip utility, iproute2-ss091226
[root@vagrant-
[root@vagrant-
foo
[root@vagrant-
[root@vagrant-
[root@vagrant-
Linux vagrant-
Are you sure that the node in which dhcp agent is running has the same version of iproute?
Another possibility would be dhcp agent is executing a different binary (if multiple versions are installed on different paths)?