While we investigate how to fix current issues including migrating to latest decanter version 2.X, we have following alternatives to keep on using the framework: - Use original decanter 1.0.X: this wo

No agenda item but FYI it is very possible we will have to disable JVM monitoring by default in all jobs. Reason being is new decanter version we are using to fix issues in master is not stable in the

Thanks Rohan, I guess we are still missing the LF credentials to push the patch. Did you finally opened a ticket to LF? otherwise I will do it.

For the yang push internship project, we still have question on how to push code from ODL to Yang github.

+1

I think we should remind all projects to check their CSIT branches after the usual branching cut in master. FYI I have always seen issues with this because the automation or the manual process (not su

Hi OFP devs, Just let you know the issue of the table stats is very apparent in master: https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-magnesium/

I think for submodules we will have to create a repo with all our models, this does not seem very dynamic + adds extra work to maintain new repo. Anil, what was the issue of having an LF ID we can use

FYI I have already merged Stanislav patches that allow projects to opt out from JVM monitoring. This means your CSIT should be working back now. Stanislav, netvirt project has filed this patch: https:

Also looping netvirt list, to see how they want to proceed here.

Thanks Jamo, I guess if netvirt project is interested in the JVM framework they can patch as you suggest, otherwise we can just disable it for netvirt so we have less things to maintain in integration

The real issue is apache decanter does not work in the latest Karaf version pulled in master. This generates an exception in the Karaf log and it seems netvirt tests are tracking and failing any test

Correct there is a time gap between 2 patches that can cause issues in some CSITs. Please revert if problem persists.

Hi everybody. FYI I just merged a patch to extend the JVM monitoring framework to all our CSIT jobs: https://git.opendaylight.org/gerrit/#/c/releng/builder/+/85398/ After this it is expected all jobs

Hi Rohan, FYI I created this patch to add the yang push action to the exiting distribution-sanity job: https://git.opendaylight.org/gerrit/#/c/releng/builder/+/85734/ Feel free to reuse or create your

I think you have to ask LF for jenkins permissions if you have not done it yet.

For this last I left a comment in this patch: https://git.opendaylight.org/gerrit/#/c/releng/builder/+/84613/ If anyone have an answer, otherwise we can redo the patch. BR/Luis

Hi everybody, FYI CSIT is broken since yesterday, I opened this ticket to LF: https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17943 BR/Luis

Actually I picked the wrong example, this build shows the error: https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-sodium/362/console

As shown here for example: https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-sodium/363 pip3 command fails: Traceback (most recent call last): File "/usr/bin