Hi Vishal. Any idea what this failure is? Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.197 sec <<< FAILURE! - in

Attention ovsdb-devs, Autorelease fluorine failed to build southbound-impl from ovsdb in build 249. Attached is a snippet of the error message related to the failure that we were able to

Hi Vishal, Your last comment from Aug 25th (long time ago) wanted Sunnelu to take a look at this patch to make sure it was good to go. I think Suneelu has been busy with other activities, and Nobin

Hi all, please get any bug fixes in before Thursday if they need to be in the fluorine-sr1 build. Please finish reviews and run the csit on the patches so they can be merged. Thanks, Sam ----------

Michael Vorburger <vorburger@...> wrote: COE is pretty much done: https://git.opendaylight.org/gerrit/76475 builds and passes its tests (with the other MRI patches). It only needs the final

Hello, Given the skipped TSC meeting yesterday, we thought it may be useful to send a quick current status update in writing re. https://jira.opendaylight.org/browse/TSC-132 (which is on

Robert Varga <nite@...> wrote: That wasn’t the problem: the problem was that Brady hadn’t locally rebuilt NETCONF with the MRI patch. Regards, Stephen

Search **/src/main/feature/feature.xml for odl-jackson, adjust it from [3.1.0,4) to [4,5). Regards, Robert

Thanks for the fix. Am working on getting rest of it working.

This change fixes that particular build failure: But, now I get this build failure, which should be an easy fix too that I'll look into now. Regards, Brady Johnson bjohnson@...

HI Brady, Yes, this is the error I too was getting and wanted help with. That is why pushed the patch so someone can help figure it out, as well asked for a session where we can just get together and

The OVSDB project is also blocking the Neon MRI version bump for the SFC project. I saw that Vishal created this patch [0], but locally for me, I get this build error: In SFC I get this error: [0]

+<tsc@...> bump... hello, anyone home at project ovsdb? ;-) just FYI the way I look at the plan, you guys are now on the "critical path" (blocking neutron -> genius -> netvirt) in the overall

OVSDB Committers and contributors, I've created Jira for OVSDB Neon release plan [1]. Please go through it and update if you want to add anything. Thanks and Regards, Vishal Thapar. [1]

Good people (committers) of OVSDB, are you planning to work on https://jira.opendaylight.org/browse/OVSDB-467 this week? I have just realized it's a (hard) dependency for

During bringup, if A depends on B, B will come up first. I expect shutdown order to be reverse, as in, A can't go while B is still up if B depends on A. I suspect that is why we're seeing the issue.

I'm not sure if / doubt that Blueprint stops things in the order you want, or how to make it do so, but perhaps the easiest is to just make it explicit? So a @PreDestroy somewhere approprriate in

It is in the cluster priority range. The graceful shutdown changes make this easy to reproduce. We can wait till DDF, but I think this will be a good one to have in place. Also related is that the

Hi Sam, Yes, we bring up the ports once everything is ready, so should bring them down before everything goes away. Michael can tell more about how order is determined by bundles, but we can figure

Vishal, Michael, when changing the 3node csit to use a graceful shutdown rather than a kill -9, I noticed the ovsdb listening on 6640 i still open while shutting down. It looks weird because as the