Hi OVSDB Team, Hi All Since today's morning with latest builds of OXYGEN and Fluorine (all branches were rebased) I always see this error in ovsdb log, when devstack executes "sudo ovs-vsctl set-manag

you have some bug in the controller, I think. There were problems recently that I *think* are fixed or getting fixed. I couldn't keep up with everything though. I don't think you are caring about the

Hello there. I've created some queues with different max and min rates and set some flows to these queues. As you can see in the files attached, I set flow from ip 192.168.56.1.1 to dest 10.0.0.5 to t

Hi, I am running GENIUS CSIT on fluorine in sandbox and I am facing an issue that port is not in listening state. https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/genius-csit-3node-sathwikg

Vishal, what do you think about the ovsdb IT? Looks like it has not been passing for a while. Other question is do we want to look at running the core csit on every patch? Looks like the csit only tak

It's already done. Maybe race condition. https://jira.opendaylight.org/projects/TSC/issues/TSC-60 Sam Hague <shague@...> wrote: -- Isaku Yamahata <isaku.yamahata@...>

Hi Vishal, As we have already discussed, genius 3 node CSIT is randomly failing, due to bridge not showing up in topology/operational DS, on delete and create of bridge. You were indicating that, the

Josh, Vivek, Vishal, could you submit the required jiras to request going managed for Fluorine? As noted in [1] the deadline was today 3/22/18 for the request. [2] is an example from NetVirt. Thanks,

Hello. I'm trying to delete some queues entries from a qos row and finally delete the qos row. I'm trying to delete them by using rest request but it doesn't seem to work. Also, I can't delete them fr

Hi Suneelu, Vic, Stephen, I was working on OVSDB Oxygen Release Notes and noticed that we have only one bug fixed in oxygen [2], likely due to rest not being tagged correctly. Can you go through list

I double checked that #215 used Oxygen RC3 and it did. All good. JamO

Hi, The lispflowmapping CSIT failed due to an infra issue, the error message in the logs is: "03:38:32 ERROR: Failed to initialize infrastructure. Reason: Timed out" -Lori

fyi, just filed: https://jira.opendaylight.org/browse/OVSDB-426 Thanks, JamO

Greetings all: Int/dist job #213 is completed and the RC3 status is updated in spreadsheet with the failed CSIT jobs. Request the below projects to update the status on the spreadsheet. * aaa * bgpcep

I think I see what he means - I can push a patch.

Hi Jamo, Could you look at failures in OVSDB CSIT [0] and update Oxygen tracking sheet [1] if those are blockers or not? There seem to be 3 extra failures as compared to Nitrogen and Oxygen. Regressio

Hi Suneelu, Can you take a look at this failure [0]? Looks like some recent patch has broken OVSDB verify builds. Regards, Vishal. [0] https://jenkins.opendaylight.org/releng/job/ovsdb-maven-verify-fl

Vishal Thapar <vishal.thapar@...> wrote: +1 Regards, Stephen

+1 Thanh

+1 -- Thanks Anil