Yes Luis.. In the above output, this is what was causing the problem external_ids :

Thanks Eric, this worked perfect.

A command like this: sudo ovs-vsctl remove open_vswitch . external-id "opendaylight-iid" will remove the instance id setting from the open_vswitch table.

Yes, you can do that for now.

OK makes sense, I will just need to find a way to reset the id in my local OVS to reproduce the CI behavior. BR/Luis

To test that, we can change the order of the test suites( connection from ODL to ovs then ovs to controller) to be assure. Should i push the patch ?

Luis, That could be it... if you create an OVSDB node with that instance id from ODL, disconnect ODL (or restart it) and reconnect. It will believe the iid stored in OVSDB rather than constructing a

I am thinking because my OVS was previously accessed from ODL, maybe something is written in the OVS that changes the behavior when the OVS connects to controller. The VMs in CI are fresh new every

open_vswitch table dump in my local system: mininet@mininet-vm:~\> sudo ovs-vsctl list open_vswitch _uuid : 8625e529-b120-425d-ae73-39757be6e38b bridges :

Hi, I tried two different cases each time I got the same result. The node-id is "ovsdb//MininetIP:6644". Case 1: Controller Robot And OVS on same machine Case 2: Controller Robot on one machine and

Luis, On your local machine, can you try 'ovsdb-client dump' command. It will dump all the tables of ovsdb database and in those table look for Open_Vswitch table and see if there is a string

Yes

Luis in both the case connection is initiated from OVS? -- Thanks Anil

Hi Anil, I have tested RC2 and also latest integration distribution from Nexus in my setup and I still see OVSDB id in the form of "node-id": "ovsdb://127.0.0.1:6644”. However in ODL CI I see the

How do I add it to the ODL google calendar? Will do it after we get the Webex.

Could we get this added to the central ODL Google Calendar as well? Ed

more details » OVSDB VTEP meeting Will update the Webex when Phil is able to provide it. WhenWeekly from 7am to 8am on Tuesday Pacific Time WhereWebex to be provided by Phil

Hi all, are there any bugs that need to be in for Lithium? Also are there any bugs that we need to release note since they will not be fixed? The final build RC2 was built last night so any

fine with me as well. -- Thanks Anil

Patches in question were merged on 2nd june (one of them was https://git.opendaylight.org/gerrit/#/c/21448/). So if you are running integration build, you need to pull the latest code integration repo