May be another issue with ovs-docker?:
Things work fine with --net=none. But I ran into this issue:
1. I create a container with --net=none.
2. I connect the vswitch to container: ovs-docker add-port
root@ashok-vb:~# ovs-docker add-port br-int eth0 25021347059d 2.2.2.2
root@25021347059d:/# ifconfig
eth0 Link encap:Ethernet HWaddr ce:96:03:03:3f:d0
inet addr:2.2.2.2 Bcast:0.0.0.0 Mask:255.255.255.255
inet6 addr: fe80::cc96:3ff:fe03:3fd0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23855 (2root@ashok-vb:~# ovs-docker del-port br-int eth0
25021347059d3.8 KB) TX bytes:828 (828.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
SO FAR SO GOOD... BUT NOW I DECIDE THAT 2.2.2.2 is the wrong address. I
want to change it to 1.1.1.2. So I do:
root@ashok-vb:~# ovs-docker del-port br-int eth0 25021347059d
root@25021347059d:/# ifconfig
eth0 Link encap:Ethernet HWaddr ce:96:03:03:3f:d0
inet addr:2.2.2.2 Bcast:0.0.0.0 Mask:255.255.255.255
inet6 addr: fe80::cc96:3ff:fe03:3fd0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:205 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37892 (37.8 KB) TX bytes:828 (828.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
ISN'T eth0 supposed to be deleted???
NOW WHEN I TRY TO ADD PORT with the address I want, it naturally complains
that "file exists" which makes sense as eth0 is still there:
root@ashok-vb:~# ovs-docker add-port br-int eth0 25021347059d 1.1.1.2
RTNETLINK answers: File exists
RTNETLINK answers: File exists
So "ovs-docker del-port..." bug? I can look at it and fix it... thought
I'll pass this by you...
On Fri, Jan 30, 2015 at 8:30 PM, Ashok Chippa <a.n.chi...@gmail.com> wrote:
> Yes, I just read this issue with routing entry on google... :) for example
> with dhcp lease renewal...
>
> Thanks for your time... appreciate it.
>
>
> On Fri, Jan 30, 2015 at 8:28 PM, Gurucharan Shetty <shet...@nicira.com>
> wrote:
>
>> On Fri, Jan 30, 2015 at 8:26 PM, Ashok Chippa <a.n.chi...@gmail.com>
>> wrote:
>> > Disclaimer: I am not a linux network expert... that's why I am
>> struggling
>> > with this a bit...
>> >
>> > root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0
>> 46524ba3123a
>> > 1.1.1.1
>> > RTNETLINK answers: File exists
>> > RTNETLINK answers: File exists
>> >
>> > I can just remove the file if I knew which file it is complaining
>> about...
>> > Would you know?
>> Such errors occur if there is a network entity that already exists and
>> you are trying to overwrite it. For e.g., trying to create a eth0
>> interface when one already exists. Or trying to se a routing entry
>> when one already exists.
>>
>> >
>> >
>> >
>> > On Fri, Jan 30, 2015 at 8:12 PM, Ashok Chippa <a.n.chi...@gmail.com>
>> wrote:
>> >>
>> >> Thanks, I figured the stray i/f issue. I looked at your script as
>> well...
>> >> quite straightforward...
>> >>
>> >> Any idea why this is happening:
>> >>
>> >> root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0
>> 46524ba3123a
>> >> 1.1.1.1
>> >> RTNETLINK answers: File exists
>> >> RTNETLINK answers: File exists
>> >>
>> >> I googled and tried different workarounds, no luck so far...
>> >>
>> >> On Fri, Jan 30, 2015 at 7:29 PM, Gurucharan Shetty <shet...@nicira.com
>> >
>> >> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Jan 30, 2015, at 5:26 PM, Ashok Chippa <a.n.chi...@gmail.com>
>> wrote:
>> >>>
>> >>> ovs-docker seems to be a bit buggy... after creating/deleting/creating
>> >>> containers, I got into a situation where a stray port on the
>> openvswitch
>> >>> remains...
>> >>>
>> >>> Before you delete the containers, do you delete the ports using
>> del-port
>> >>> command? Stray ports can remain if you dont do that.
>> >>>
>> >>> It is a very simple script that you should be able to debug easily.
>> >>>
>> >>>
>> >>> root@ashok-vb:~# ifconfig
>> >>>
>> >>> c7ef9934c0e44_l Link c7ef9934c0e44encap:Ethernet HWaddr
>> >>> ca:40:32:35:a6:8c
>> >>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>> >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> >>> collisions:0 txqueuelen:1000
>> >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>> >>>
>> >>> docker0 Link encap:Ethernet HWaddr 56:84:7a:fe:97:99
>> >>> ...
>> >>>
>> >>> How do I delete c7ef9934c0e44? This was previously created by
>> ovs-docker
>> >>> command...
>> >>>
>> >>> It is a veth interface. You can delete it using 'ip'.
>> >>>
>> >>>
>> >>> On Fri, Jan 30, 2015 at 5:01 PM, Ashok Chippa <a.n.chi...@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi Gurucharan,
>> >>>>
>> >>>> Any idea how to work around this issue:
>> >>>>
>> >>>> root@ashok-vb:/usr/local/bin# ovs-docker add-port br-int eth0
>> >>>> 46524ba3123a 1.1.1.1
>> >>>> RTNETLINK answers: File exists
>> >>>> RTNETLINK answers: File exists
>> >>>>
>> >>>> I reinstalled the openvswitch and recreated the containers and tried
>> >>>> ovs-docker again and ran into this... Any idea to clear the old
>> stuff and
>> >>>> start over?
>> >>>>
>> >>>> Appreciate your help.
>> >>>>
>> >>>> Thanks,
>> >>>> Ashok
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> discuss mailing list
>> >>> discuss@openvswitch.org
>> >>> http://openvswitch.org/mailman/listinfo/discuss
>> >>
>> >>
>> >
>>
>
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
