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 instance won't come down, it just takes more time than the tests are waiting for and it obviously depends on the number of features installed.

Bye,
Robert (offline for real)



Sent from my BlackBerry - the most secure mobile device - via the Orange Network


  Original Message  



From: faseela.k@...
Sent: August 7, 2019 8:33 AM
To: nite@...; jluhrsen@...; r.p.karthika@...; integration-dev@...
Cc: odlparent-dev@...; mdsal-dev@...
Subject: RE: [integration-dev] Karaf stop command not working in Sodium.


Robert,
   We tried downloading the same distro and tested things manually, but we are not able to reproduce the issue.
   But this is failing most of the times in Jenkins.
   And can you tell us how to test this with a WIP patch in mdsal? [0]
   How do we test this without having version bump patches in all projects?
   Also, why did this break all of a sudden?
Thanks,
Faseela

[0] https://protect2.fireeye.com/url?k=c9282245-95a2f684-c92862de-863d9bcb726f-82981d78e3f8a352&q=1&u=https%3A%2F%2Fgit.opendaylight.org%2Fgerrit%2Fc%2Fmdsal%2F%2B%2F83493


-----Original Message-----
From: Robert Varga <nite@...>
Sent: Tuesday, August 6, 2019 11:20 PM
To: Jamo Luhrsen <jluhrsen@...>; Faseela K <faseela.k@...>; R P Karthika . <r.p.karthika@...>; 'integration-dev@...' (integration-dev@...) (integration-dev@...) <integration-dev@...>
Cc: odlparent-dev@...; mdsal-dev@...
Subject: Re: [integration-dev] Karaf stop command not working in Sodium.

On 05/08/2019 21:42, Jamo Luhrsen wrote:

is this enough info?

thread dump before running robot:
 
https://protect2.fireeye.com/url?k=df2b6581-83a1b140-df2b251a-863d9bcb
726f-2daec84e911dd818&q=1&u=https%3A%2F%2Flogs.opendaylight.org%2Frele
ng%2Fvex-yul-odl-jenkins-1%2Fgenius-csit-1node-upstream-only-sodium%2F
274%2Fodl_1%2Fkaraf_1_10983_threads_before.log.gz
<https://protect2.fireeye.com/url?k=d87dd00d-84f704cc-d87d9096-863d9bc
b726f-9bd20260a15f63a1&q=1&u=https%3A%2F%2Flogs.opendaylight.org%2Frel
eng%2Fvex-yul-odl-jenkins-1%2Fgenius-csit-1node-upstream-only-sodium%2
F274%2Fodl_1%2Fkaraf_1_10983_threads_after.log.gz>

^^^ your email client has betrayed you :)

thread dump after running robot:
 
https://protect2.fireeye.com/url?k=ab2c8fe8-f7a65b29-ab2ccf73-863d9bcb
726f-611852abf170af25&q=1&u=https%3A%2F%2Flogs.opendaylight.org%2Frele
ng%2Fvex-yul-odl-jenkins-1%2Fgenius-csit-1node-upstream-only-sodium%2F
274%2Fodl_1%2Fkaraf_1_10983_threads_after.log.gz

I'm not really sure what to look for, but really curious.

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 probably a side-effect of
https://protect2.fireeye.com/url?k=b64f59e5-eac58d24-b64f197e-863d9bcb726f-ae28518222c47c71&q=1&u=https%3A%2F%2Fjira.opendaylight.org%2Fbrowse%2FMDSAL-461 fix, we have a slight optimization already staged for mdsal-4.0.4, but this needs proper looking after.

Can you file an issue with mdsal?

Also, can you try with https://protect2.fireeye.com/url?k=c9282245-95a2f684-c92862de-863d9bcb726f-82981d78e3f8a352&q=1&u=https%3A%2F%2Fgit.opendaylight.org%2Fgerrit%2Fc%2Fmdsal%2F%2B%2F83493 ?

I'll take a look next week, as I am going offline.

Regards,
Robert