Michael Vorburger <vorburger@...> wrote: Yes, it’s caused by the bump; the bump is now complete, so you shouldn’t see this again. Regards, Stephen

+Kitt, Stephen +Robert Varga SingleFeatureTest (SFT) failure due to: org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root] osgi.identity;

Hi, any idea why daexim distribution-check is failing on oxygen

Mohamed, You can take a look at this log, where the issue was reproduced.

Hi Sam, We need to solve the prefix between these 2 distinct projects. The issue you are seeing is that the "project-view" template creates a view with the name of whatever value you pass to

Thanh, is there a way to use the same project for a name? The patch [1] to add jobs for the new ansible project, where I used the typical name of the project as the keys. This blows up though, because

Hi Faseela, I cannot reproduce the error in my local it just work fine. I re-push it again at [0], during our last COE meeting you mentioned that we have build manually the golang binary before run

The below patch has been reverted, and after that CSIT is running fine. I did not get time to dig into understand what exactly is causing the

I am unable to figure out what is happening may need to work with the IT/infra or vex team, one option is updating the resources on the Nexus node. However, I am fully _not_ convinced that this will

Please keep reporting these issues to https://jira.linuxfoundation.org/browse/RELENG-1215 adding Anil since he's been investigating this issue. Anil, We are still seeing these gateway timeouts. Have

also, here's a job with the same problem on the releng

I've had a couple jobs in a row (csit jobs in the sandbox) not able to fully upload logs to the logs server. I'm not able to debug my problem because of it. I think this is sort of a wide ranging

I didn't see any replies to this thread, but since integration-dev was on the To: list, I took a quick look. Seems likely a problem in COE and not the test, right? I see things in karaf.log like

4. post-plan 1 and 2 can both be ran - it all depends if the job yaml sets them or has one defined. There is also a post-plan. They are used to configure ODL or the tests - either before starting it

Yes. It's the 3.1.4 bump. Robert put a patch to fix it but it's not merged

Hello, anyone knows what caused e.g. neutron-distribution-check-fluorine to suddenly break? https://git.opendaylight.org/gerrit/#/c/77569/ =>

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