Empty lists are disappearing in Neon: https://lists.opendaylight.org/pipermail/yangtools-dev/2018-September/002308.html, so this is fully expected. Regards, Robert

As Jamo said, we are late on our targeted release date, but we are also cutting it tight with the marketing release date which is on Tuesday.

Isn't this one of the changes that came in Neon, where an empty list now returns null/404 instead of emtpy list? I think we ran into similar issue in another test back in Oct/Nov [can't recall] where

I'm digging through the neon csit failures to help sign off for the release, and came across a failure in neon csit that is not there in fluorine. We need to explain it or fix it so we can get the

Looks like the patch upstream has been merged and is in our csit jobs now, so they pass.

Yeah, the main netvirt jobs don't spin up the tools vms. As Venkat mentions the tools_count is 0.

Hi Anil, I think the count is zero, It is not spinning up any VM with that image. -- Regards, Venkatrangan G

Hi Venkat: Good point. on job no [3.], if we are not using the mininet image we should consider removing that from the job{s}. From the logs we can see its booting up test VM/node and not really using

Hi Anil, Just started reviewing the patches. I think the job [3] does not use any mininet image. There are many other jobs like BGPCEP jobs that will use other components like exabgp. They

+int/dev lists Thanks, Anil

Hi Everyone, I'm still up at 12 am so don't worry about it, not a problem for me, I can make it work. Regards, Thanh

OK, looks like the patch has merged in openstack side. Any idea how long that takes before we have the updates in CSIT? The neon RC's are blocked on this since those jobs failed. We need to rerun the

Ohh okay! Is it okay then if I sync up with Karthika offline, in case I won't be able to make it regularly? Thanks, Faseela

Well, this is going to be awful time for Thanh (12:00 AM), any chance you can make it it earlier?

Thanks a lot Daniel! -Lori

Look into the stack.log in the compute_1 folder. At the very bottom you will see why the stack failed. Might be related to the jjb stuff, but that log details what failed.

Hi, The jobs will stack successfully once this patch gets merged - [0]. The git uses a wrong option in control node. [0] - https://review.openstack.org/#/c/642927/ -- Regards, Venkatrangan G

Hi Karthika: Are you using the right version of the snapshot in your pom files, because the maven metadata files does not exist on Nexus? +Luis Thanks, Anil

Sorry for the lag Lori, it's merged now. Thanks, Daniel On Thu, Mar 14, 2019 at 8:13 AM Lori Jakab <lorand.jakab+odl@...> wrote:

Sorry, I just saw there was an unanswered comment which I now answered.