[release] Sulfur code freeze


Daniel de la Rosa
 



On Tue, Apr 26, 2022 at 12:55 PM Robert Varga <nite@...> wrote:
On 15/04/2022 02:23, Daniel de la Rosa wrote:
> Anyhow, Integration test for AR#15 still has some issues
>
> https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/200/
> <https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/200/>
>
> Should we just move forward like this?

So we have latest AR here:
https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/

Triggered by Sangwook, because the previous run failed. We can expect
AR #30 in ~4 hours and test results from that in another ~3 hours.

Based on the results of
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/219/,
the release is GO from my perspective.

There seem to be OFP issues, though, I think Sangwook has the final say.

ok  @Ha, Sangwook and all TSC, if you are ok with releasing Sulfur in its current state, AR#30 and integration #220, please approve it at 

I'll also send another email just for the approval

Thank you all



On the BGPCEP side of things, we have two failures:
1. one of them is a BGP policy 409, which I need to investigate, but I
do not believe it's anything major
2. BGP ingest is plagued by
https://jira.opendaylight.org/browse/CONTROLLER-2043, but I honestly
think this is an environment issue

At any rate, looking at the schedule, we are *way* past the release date
and in fact should be releasing Sulfur SR1 on 4/28, i.e. in two days.

I think we should just release as is, get the marketing stuff out, etc.
and circle back for SR1 -- say, in two weeks. That would give us a few
days of breathing time (I know I need some) and see what's what.

We also are ~2 weeks past the Chlorine MRI bump, so that switching gears
makes a ton of sense -- I really want Chlorine to get us back on track
with the calendar :)

Regards,
Robert


Robert Varga
 

On 15/04/2022 02:23, Daniel de la Rosa wrote:
Anyhow, Integration test for AR#15 still has some issues
https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/200/ <https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/200/>
Should we just move forward like this?
So we have latest AR here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/29/

Triggered by Sangwook, because the previous run failed. We can expect AR #30 in ~4 hours and test results from that in another ~3 hours.

Based on the results of https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/219/, the release is GO from my perspective.

There seem to be OFP issues, though, I think Sangwook has the final say.

On the BGPCEP side of things, we have two failures:
1. one of them is a BGP policy 409, which I need to investigate, but I do not believe it's anything major
2. BGP ingest is plagued by https://jira.opendaylight.org/browse/CONTROLLER-2043, but I honestly think this is an environment issue

At any rate, looking at the schedule, we are *way* past the release date and in fact should be releasing Sulfur SR1 on 4/28, i.e. in two days.

I think we should just release as is, get the marketing stuff out, etc. and circle back for SR1 -- say, in two weeks. That would give us a few days of breathing time (I know I need some) and see what's what.

We also are ~2 weeks past the Chlorine MRI bump, so that switching gears makes a ton of sense -- I really want Chlorine to get us back on track with the calendar :)

Regards,
Robert


Daniel de la Rosa
 



On Thu, Apr 14, 2022 at 11:38 AM Robert Varga <nite@...> wrote:
On 13/04/2022 17:04, Daniel de la Rosa wrote:
>
>
> Hello all,  any update on this? Sulfur integration test are still in bad
> shape

So we still do not have that ticket taken care of, but I realized we can
work it around by changing the builders -- which we did and I spent
today releasing MRI projects, which are now integrated.

I have kicked off an AR ahead of schedule here:
https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/15/

It should complete just fine and the test results should come back in a
much more reasonable shape -- most likely good enough to finally cut the

Yes Anil is out this week so maybe @Andrew Grimberg can get somebody else to help with 

Anyhow, Integration test for AR#15 still has some issues 


Should we just move forward like this?

 

branch.

Regards,
Robert

> On Wed, Apr 6, 2022 at 4:04 PM Daniel de la Rosa via
> lists.opendaylight.org <http://lists.opendaylight.org>
> <ddelarosa0707=gmail.com@...
> <mailto:gmail.com@...>> wrote:
>
>     Great, thanks for the update.
>
>     On Wed, Apr 6, 2022 at 1:13 AM Robert Varga <nite@...
>     <mailto:nite@...>> wrote:
>
>         On 06/04/2022 01:21, Daniel de la Rosa wrote:
>          > Hello Robert and all
>          >
>          > it looks like we still have several issues
>          >
>          >
>         https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
>         <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>
>
>          >
>         <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
>         <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>>
>          >
>          > are we still tracking some of these issues in jira tickets?
>
>         Yes, I think most of the issues are already fixed, but I am
>         waiting for
>         https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826
>         <https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826>
>
>         to issue the corresponding releases.
>
>         With the upgrade guide complete, I think we are good to branch,
>         though.
>
>
>     Ok it looks like @Anil Belur <mailto:abelur@...> is
>     still working on this issue so let's see if we can get an update shortly
>
>
>
>         Regards,
>         Robert
> >


Robert Varga
 

On 13/04/2022 17:04, Daniel de la Rosa wrote:
Hello all,  any update on this? Sulfur integration test are still in bad shape
So we still do not have that ticket taken care of, but I realized we can work it around by changing the builders -- which we did and I spent today releasing MRI projects, which are now integrated.

I have kicked off an AR ahead of schedule here: https://jenkins.opendaylight.org/releng/job/autorelease-release-sulfur-mvn38-openjdk11/15/

It should complete just fine and the test results should come back in a much more reasonable shape -- most likely good enough to finally cut the branch.

Regards,
Robert

On Wed, Apr 6, 2022 at 4:04 PM Daniel de la Rosa via lists.opendaylight.org <http://lists.opendaylight.org> <ddelarosa0707=gmail.com@... <mailto:gmail.com@...>> wrote:
Great, thanks for the update.
On Wed, Apr 6, 2022 at 1:13 AM Robert Varga <nite@...
<mailto:nite@...>> wrote:
On 06/04/2022 01:21, Daniel de la Rosa wrote:
> Hello Robert and all
>
> it looks like we still have several issues
>
>
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>

>
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>>
>
> are we still tracking some of these issues in jira tickets?
Yes, I think most of the issues are already fixed, but I am
waiting for
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826
<https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826>
to issue the corresponding releases.
With the upgrade guide complete, I think we are good to branch,
though.
Ok it looks like @Anil Belur <mailto:abelur@...> is
still working on this issue so let's see if we can get an update shortly
Regards,
Robert


Daniel de la Rosa
 



Hello all,  any update on this? Sulfur integration test are still in bad shape



On Wed, Apr 6, 2022 at 4:04 PM Daniel de la Rosa via lists.opendaylight.org <ddelarosa0707=gmail.com@...> wrote:
Great, thanks for the update.

On Wed, Apr 6, 2022 at 1:13 AM Robert Varga <nite@...> wrote:
On 06/04/2022 01:21, Daniel de la Rosa wrote:
> Hello Robert and all
>
> it looks like we still have several issues
>
> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>
>
> are we still tracking some of these issues in jira tickets?

Yes, I think most of the issues are already fixed, but I am waiting for
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826
to issue the corresponding releases.

With the upgrade guide complete, I think we are good to branch, though.

Ok it looks like @Anil Belur is still working on this issue so let's see if we can get an update shortly



Regards,
Robert


Daniel de la Rosa
 

Great, thanks for the update.

On Wed, Apr 6, 2022 at 1:13 AM Robert Varga <nite@...> wrote:
On 06/04/2022 01:21, Daniel de la Rosa wrote:
> Hello Robert and all
>
> it looks like we still have several issues
>
> https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/
> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>
>
> are we still tracking some of these issues in jira tickets?

Yes, I think most of the issues are already fixed, but I am waiting for
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826
to issue the corresponding releases.

With the upgrade guide complete, I think we are good to branch, though.

Ok it looks like @Anil Belur is still working on this issue so let's see if we can get an update shortly



Regards,
Robert


Robert Varga
 

On 06/04/2022 01:21, Daniel de la Rosa wrote:
Hello Robert and all
it looks like we still have several issues
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sulfur/190/>
are we still tracking some of these issues in jira tickets?
Yes, I think most of the issues are already fixed, but I am waiting for https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826 to issue the corresponding releases.

With the upgrade guide complete, I think we are good to branch, though.

Regards,
Robert


Daniel de la Rosa
 



On Fri, Apr 1, 2022 at 4:11 PM Robert Varga <nite@...> wrote:
On 31/03/2022 17:41, Robert Varga wrote:
> Alright, everything has been merged up.
>
> int/dist and autorelease need to have their jobs updated to use
> maven-3.8, please review the patches here:
>
> https://git.opendaylight.org/gerrit/c/releng/builder/+/100304
> https://git.opendaylight.org/gerrit/c/releng/builder/+/100306
>
> I am writing up the release notes and upgrade guide next.

So looking at
https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/185/
we have plenty of badness.

The core problem is that a ton of test suites are depending on
OPERATIONAL_API, which points to old RESTCONF, which is no longer
installed by default. I have
https://git.opendaylight.org/gerrit/c/releng/builder/+/100359 to install
it for now, but we need to eventually (very soon) ditch it.

Luis, any idea on how to fix that in a sensible manner?

Also, RF is now reporting a ton of ugly 'Keyword 'BuiltIn.Run Keyword
Unless' is deprecated.' messages -- I'll take a peek next week unless
somebody beats me to it.

Finally, I am tracking two regressions in MD-SAL (already fixed) and one
in NETCONF (next on the list), but I'd like to get a better reading on
CSIT before rolling out the corresponding releases out.


Hello Robert and all 

it looks like we still have several issues
 

are we still tracking some of these issues in jira tickets? 
 

Regards,
Robert


Robert Varga
 

On 31/03/2022 17:41, Robert Varga wrote:
Alright, everything has been merged up.
int/dist and autorelease need to have their jobs updated to use maven-3.8, please review the patches here:
https://git.opendaylight.org/gerrit/c/releng/builder/+/100304
https://git.opendaylight.org/gerrit/c/releng/builder/+/100306
I am writing up the release notes and upgrade guide next.
So looking at https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/185/ we have plenty of badness.

The core problem is that a ton of test suites are depending on OPERATIONAL_API, which points to old RESTCONF, which is no longer installed by default. I have https://git.opendaylight.org/gerrit/c/releng/builder/+/100359 to install it for now, but we need to eventually (very soon) ditch it.

Luis, any idea on how to fix that in a sensible manner?

Also, RF is now reporting a ton of ugly 'Keyword 'BuiltIn.Run Keyword Unless' is deprecated.' messages -- I'll take a peek next week unless somebody beats me to it.

Finally, I am tracking two regressions in MD-SAL (already fixed) and one in NETCONF (next on the list), but I'd like to get a better reading on CSIT before rolling out the corresponding releases out.

Regards,
Robert


Daniel de la Rosa
 

Thanks Robert... 

On Thu, Mar 31, 2022 at 8:41 AM Robert Varga <nite@...> wrote:
On 31/03/2022 01:20, Robert Varga wrote:
> On 29/03/2022 01:13, Robert Varga wrote:
>> On 28/03/2022 00:10, Robert Varga wrote:
>>> On 24/03/2022 01:24, Daniel de la Rosa wrote:
>>>>
>>>>
>>>> On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@...
>>>> <mailto:nite@...>> wrote:
>>>> That’s impressive. Ok thanks and it is all good. We will have a very
>>>> solid sulfur release
>>>
>>> A quick update here. We are on the home stretch now, with 31
>>> callsites still being bad. About a third are duplicate (e.g. they are
>>> the same weirdness across bierman20/rfc8040). They will need some
>>> amount of TLC, which I am not in position to give right now, sorry :(
>>
>> Okay, so I am down to 3 call sites, which fall into two categories:
>>
>> 1. old RESTCONF's URI parser leafref support. I think I can perform
>> sufficient surgery to make this work without having to rewrite that
>> thing (as was done for new RESTCONF, where this is a breeze)
>>
>> 2. two instances of a weird interaction with XML codec. It is not that
>> weird, I understand what is going on, it just needs a bit of more work.
>>
>> I will need another day to deal with them and, fingers crossed, UTs
>> should agree.
>
> This is now cleared, netconf-3.0.0 is out there. Most of the MSI update
> patches are done -- except openflowplugin.
>
> Upgraded spotbugs is finding some badness which was introduced in
> https://git.opendaylight.org/gerrit/c/openflowplugin/+/91313 and I need
> to figure out how to fix it.
>
> BGPCEP still has a four contributions left for review, I will take care
> of that tomorrow.

Alright, everything has been merged up.

int/dist and autorelease need to have their jobs updated to use
maven-3.8, please review the patches here:

https://git.opendaylight.org/gerrit/c/releng/builder/+/100304
https://git.opendaylight.org/gerrit/c/releng/builder/+/100306

I am writing up the release notes and upgrade guide next.


Ok great. @Anil Belur and/or @Luis Gomez  maybe you can take a look at this 

 

Bye,
Robert


Robert Varga
 

On 31/03/2022 01:20, Robert Varga wrote:
On 29/03/2022 01:13, Robert Varga wrote:
On 28/03/2022 00:10, Robert Varga wrote:
On 24/03/2022 01:24, Daniel de la Rosa wrote:


On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :(
Okay, so I am down to 3 call sites, which fall into two categories:

1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze)

2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work.

I will need another day to deal with them and, fingers crossed, UTs should agree.
This is now cleared, netconf-3.0.0 is out there. Most of the MSI update patches are done -- except openflowplugin.
Upgraded spotbugs is finding some badness which was introduced in https://git.opendaylight.org/gerrit/c/openflowplugin/+/91313 and I need to figure out how to fix it.
BGPCEP still has a four contributions left for review, I will take care of that tomorrow.
Alright, everything has been merged up.

int/dist and autorelease need to have their jobs updated to use maven-3.8, please review the patches here:

https://git.opendaylight.org/gerrit/c/releng/builder/+/100304
https://git.opendaylight.org/gerrit/c/releng/builder/+/100306

I am writing up the release notes and upgrade guide next.

Bye,
Robert


Robert Varga
 

On 29/03/2022 01:13, Robert Varga wrote:
On 28/03/2022 00:10, Robert Varga wrote:
On 24/03/2022 01:24, Daniel de la Rosa wrote:


On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :(
Okay, so I am down to 3 call sites, which fall into two categories:
1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze)
2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work.
I will need another day to deal with them and, fingers crossed, UTs should agree.
This is now cleared, netconf-3.0.0 is out there. Most of the MSI update patches are done -- except openflowplugin.

Upgraded spotbugs is finding some badness which was introduced in https://git.opendaylight.org/gerrit/c/openflowplugin/+/91313 and I need to figure out how to fix it.

BGPCEP still has a four contributions left for review, I will take care of that tomorrow.

Regards,
Robert


Robert Varga
 

On 28/03/2022 00:10, Robert Varga wrote:
On 24/03/2022 01:24, Daniel de la Rosa wrote:


On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :(
Okay, so I am down to 3 call sites, which fall into two categories:

1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze)

2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work.

I will need another day to deal with them and, fingers crossed, UTs should agree.

Regards,
Robert


Robert Varga
 

On 24/03/2022 01:24, Daniel de la Rosa wrote:
On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amount of TLC, which I am not in position to give right now, sorry :(

I expect to have them cleared tomorrow, Tuesday the latest, at which point I'll activate the supercommitter rights and roll things out.

The upgrade guide will come right after that, e.g. Tue or Wed.

Regards,
Robert


Olivier Dugeon
 

Hello Robert, all,

Le 21/03/2022 à 15:17, Robert Varga a écrit :
On 21/03/2022 14:45, Olivier Dugeon via lists.opendaylight.org wrote:

bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.

Not yet for BGPCEP. I discover some late bugs on new PCE server last week. Patch is ready. I'll submit it this afternoon, just right after last verification.

Latest patches have been submitted:

The first two have been reviewed and are ready to be merged. Latest one needs to be reviewed.

The only point that is remaining for BGPCEP, is to clean the compilation from various warning message. I don't know if we include these now or wait for Sulfur SR1.

Regards

Olivier


Alright, anyway it's going to take a couple of days to sort out the RESTCONF stuff, so that (and the javadoc jobs) are the real blockers.

Regards,
Robert
--
Orange logo

 

Olivier Dugeon
Orange Expert, Future Networks
Open Source Referent
Orange/IMT/OLN/WTC/IEE/iTeQ

 

fixe : +33 2 96 07 28 80
mobile : +33 6 82 90 37 85
olivier.dugeon@...
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Daniel de la Rosa
 



On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@...> wrote:
On 21/03/2022 14:24, Robert Varga wrote:
> On 20/03/2022 19:50, Robert Varga wrote:
>> On 19/03/2022 16:37, Daniel de la Rosa wrote:
>>>
>>>     Alright, so MDSAL-731 is fixed and it makes MDSAL-735 more
>>> diagnosable
>>>     -- I plan to squash that today.
>>>
>>>
>>> It looks like all issues have been resolved. So are we ready to pick
>>> the next AR as RC?
>>
>> I am still working through netconf/bgpcep, plus the bump to MSI
>> projects. I'll keep you posted.
>
> bgpcep is ready for integration, but netconf is not -- as it turns the
> vast majority of patches dealing with SchemaNode.getPath() caller
> removal had to be reverted because ... let's say they were naive.

So fixing RESTCONF here is going to require a yangtools-8.0.2 release.
The problem is that we lost a DataSchemaContextTree capability which was
provided indirectly via SchemaNode.getPath() -- the details are in
YANGTOOLS-1412.

I expect to have that fixed today and finish the RESTCONF integration
tomorrow, so that the MRI bump should (fingers crossed) over the weekend.

It is way later than planned, expected or hoped, but unfortunately it is
what it is. There is silver lining here, though: this effort found two
bugs that have been squashed after lurking around for 7 years.

That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release 




I'll keep you posted,
Robert
--
Daniel de la Rosa
ODL Release Manager


Robert Varga
 

On 21/03/2022 14:24, Robert Varga wrote:
On 20/03/2022 19:50, Robert Varga wrote:
On 19/03/2022 16:37, Daniel de la Rosa wrote:

    Alright, so MDSAL-731 is fixed and it makes MDSAL-735 more diagnosable
    -- I plan to squash that today.


It looks like all issues have been resolved. So are we ready to pick the next AR as RC?
I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted.
bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.
So fixing RESTCONF here is going to require a yangtools-8.0.2 release. The problem is that we lost a DataSchemaContextTree capability which was provided indirectly via SchemaNode.getPath() -- the details are in YANGTOOLS-1412.

I expect to have that fixed today and finish the RESTCONF integration tomorrow, so that the MRI bump should (fingers crossed) over the weekend.

It is way later than planned, expected or hoped, but unfortunately it is what it is. There is silver lining here, though: this effort found two bugs that have been squashed after lurking around for 7 years.

I'll keep you posted,
Robert


Robert Varga
 

On 21/03/2022 14:45, Olivier Dugeon via lists.opendaylight.org wrote:

bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.
Not yet for BGPCEP. I discover some late bugs on new PCE server last week. Patch is ready. I'll submit it this afternoon, just right after last verification.
Alright, anyway it's going to take a couple of days to sort out the RESTCONF stuff, so that (and the javadoc jobs) are the real blockers.

Regards,
Robert


Olivier Dugeon
 

Hello Robert,

Le 21/03/2022 à 14:24, Robert Varga a écrit :
On 20/03/2022 19:50, Robert Varga wrote:
On 19/03/2022 16:37, Daniel de la Rosa wrote:

    Alright, so MDSAL-731 is fixed and it makes MDSAL-735 more diagnosable
    -- I plan to squash that today.


It looks like all issues have been resolved. So are we ready to pick the next AR as RC?

I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted.

bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.

Not yet for BGPCEP. I discover some late bugs on new PCE server last week. Patch is ready. I'll submit it this afternoon, just right after last verification.

Regards

Olivier


serviceutils is also ready to integrate, but there's a problem needing action in global-jjb: javadocs jobs are using mvn35 and thus end up exploding like here: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/32/

Even when we tell the job to use mvn38, it will unpack the correct maven, but will attempt to use mvn35: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/33/console

Regards,
Robert





--
Orange logo

 

Olivier Dugeon
Orange Expert, Future Networks
Open Source Referent
Orange/IMT/OLN/WTC/IEE/iTeQ

 

fixe : +33 2 96 07 28 80
mobile : +33 6 82 90 37 85
olivier.dugeon@...
_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Robert Varga
 

On 20/03/2022 19:50, Robert Varga wrote:
On 19/03/2022 16:37, Daniel de la Rosa wrote:

    Alright, so MDSAL-731 is fixed and it makes MDSAL-735 more diagnosable
    -- I plan to squash that today.


It looks like all issues have been resolved. So are we ready to pick the next AR as RC?
I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted.
bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naive.

serviceutils is also ready to integrate, but there's a problem needing action in global-jjb: javadocs jobs are using mvn35 and thus end up exploding like here: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/32/

Even when we tell the job to use mvn38, it will unpack the correct maven, but will attempt to use mvn35: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/33/console

Regards,
Robert