Baseline distro will not have the change until mdsal-4.0.4 is released and integrated (just as any MRI project), hence I would suggest manual testing, as noted in a separate email in this thread befor

MDSAL-466 Still waiting for feedback... Regards, Robert

Checkout v4.0.3 mdsal tag, cherry-pick the patch, build affected component, replace the jar in the distro. I am sure there is also an automated way, but Luis knows the details. And it's not that the i

^^^ your email client has betrayed you :) Yeah, kinda ... since build #273 it looks like "Framework stop" is creating SchemaContexts. It really should not, as we should be speedily stopping. This is p

Not an odlparent problem: [...] The only explanation is that there is a non-daemon thread holding down the JVM. Please do dump the threads to make sense of this. Regards, Robert

I have this: That does look like a routing problem. Since people can run the command fine, it has to be something between our workers and the Internet... Regards, Robert

Hello, https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-sodium/62/console just failed with: This looks like a problem between the job and gerrit -- and my guess

Since we are asking for 3.1.x, I think we should push for August... Regards, Robert

I don't know, either, but at least these: boil down to: updateRemoteAclCache(acl.getAccessListEntries().getAce(), aclName, AclServiceManager.Action.REMOVE); where getAccessListEntries() will return nu

Not sure there is an explicit document. The next step is to run a multipatch -- running here: https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-fluorine/298/ The job output needs

Hey everyone, we do have autorelease-openjdk11, but we are not running any CSIT with JRE 11. Given that we're very likely to switch to Java 11+ in Magnesium, which will change the default garbage coll

Both odlparent-3.1.8 and yangtools-2.0.21 are out there, now it's up to someone to raise/merge the patches to integrate them -- just like https://git.opendaylight.org/gerrit/#/q/topic:mri-fluorine-sr3

Yes, and not only anonymous but also other customer's access :) Regards, Robert

Thanks for confirming. The request to release odlparent-3.1.8 with this upgrade is here: https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-16534 Regards, Robert

Oh drat, there seems to be always something :( another reason to spin SR4... Thanks, Robert

That's 8 +1s (Abhjit, Thanh, Faseela, Luis, Anil Belur, Anil Vishnoi, Stephen and myself) and therefore it carries. Regards, Robert

+1 Regards, Robert

Honestly, given TSC's approval: AGREED: The TSC approves build 143 as the Fluorine SR3 build, pending CSIT jobs (abhijitk, 16:26:08) I would propose to just release SR3 and make it the TSC's decision

... and we're back in business: https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-managed-neon/ Thanks, Robert

AFAICT, this requires: - releasing odlparent-3.1.8 - creating version bump patches for all projects - releasing yangtools-2.0.21 - creating version bump patches for all projects - merging both sets of