Hi Everyone, I'm trying to understand the different CSIT test plans and how they all interact with each other. I see that there are 4 plans defined in CSIT. 1. script-plan 2. config-plan 3.

This is preventing us from pulling in our view-templates from this patch https://git.opendaylight.org/gerrit/77599 because defaults.yaml is causing our view-templates to require all of the CSIT

Thanh, I think Sam was going to run a sandbox or two with something more than AAA with your changes to makes sure things are working. Was something broken here though, that needed this done quickly?

It means int/dist has a wrong property: https://git.opendaylight.org/gerrit/77687 Bye, Robert

Hi Everyone, Can integration folks review and merge this set of patches with priority? https://git.opendaylight.org/gerrit/#/q/topic:revert-testplan This reverts csit templates adding nested variables

Taking a look at the logs at [0], I can see that there is some issue in the external iface-id being set for the veth ports, sometimes two ports are getting the same external-id. [0]

Mohamed, Looks like COE CSIT is broken after some recent patches were merged [0] or [1] in coe. Will need your help to understand if there is something we have to change in CSIT to

I think it comes down to the fact that pip had trouble installing something when it was setting itself up to push the logs. Since that failed, it didn't figure out the logs location and

Hello, what does the "unstable" failure on https://jenkins.opendaylight.org/releng/job//168/ mean? Tx, M. -- Michael Vorburger, Red Hat vorburger@... | IRC: vorburger @freenode | ~ =

another: https://jenkins.opendaylight.org/releng/job/controller-csit-3node-rest-clust-cars-perf-tell-only-fluorine/100/console JamO

here it is in a 1node controller CSIT job: https://jenkins.opendaylight.org/releng/job/controller-csit-1node-benchmark-all-fluorine/213/console JamO

Yeah, I saw this is a job and dismissed it as an infra instability and didn't look any deeper. I think it was a 3node netvirt csit job. I will keep an eye out for it happening more. JamO

Adding integration-dev as I don't think this is an infra issue. I did some triaging and found the following: 1. Robot vm is still running and ssh is still accessible when failure occurs 2. CPU / RAM /

found the bug. let's see if I can do my first upstream robotframework contribution: https://github.com/robotframework/SSHLibrary/issues/279 JamO

Jamo's fat finger and 2 overlooked committers are to blame here :)

So, ummm... Not sure who's fault this is, but Sam was the person that clicked submit. blame Sam. fix is here: https://git.opendaylight.org/gerrit/#/c/77465/ :) JamO

thanks for digging in to the CSIT side. something is broken there. I'll dig. JamO

This message looks like it has something to do with diagstatus ... but I don't see any real datastore errors on

+BGPCEP Claudio David Gasparini Senior Software Engineer PANTHEON technologies s.r.o. Mlynské Nivy 56, 821 05 Bratislava Slovakia Tel / +421 220 665 111 MAIL /

Jamo, Thanks for the heads-up and the first patch. I'll look into this today, and get it all into shape ASAP. Regards, Brady