[ovs-discuss] ovs-docker question

[Gurucharan Shetty]

On Fri, Jan 30, 2015 at 8:26 PM, Ashok Chippa <a.n.chippa at gmail.com> wrote:
> Disclaimer: I am not a linux network expert... that's why I am struggling
> with this a bit...
>
> root at 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.chippa at 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 at 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 <shettyg at nicira.com>
>> wrote:
>>>
>>>
>>>
>>> On Jan 30, 2015, at 5:26 PM, Ashok Chippa <a.n.chippa at 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 at 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.chippa at gmail.com>
>>> wrote:
>>>>
>>>> Hi Gurucharan,
>>>>
>>>> Any idea how to work around this issue:
>>>>
>>>> root at 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 at openvswitch.org
>>> http://openvswitch.org/mailman/listinfo/discuss
>>
>>
>