On 22/11/2021 23:11, Daniel de la Rosa wrote:

it seems that there are still BGPCEP, OVSDB and OFP issues
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

Okay, so BGPCEP should be all clear, the RESTCONF regression blocking OFP perf tests is resolved.

One of the OVSDB failures has a controller tracker, but we won't be able to fix it for SR1.

Th eonly outstanding item I am currently tracking is this: https://git.opendaylight.org/gerrit/c/integration/test/+/98642

Luis, can you review it, please?

Thanks,
Robert

On 22/11/2021 23:11, Daniel de la Rosa wrote:

it seems that there are still BGPCEP, OVSDB and OFP issues
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

On the OFP side, we have a RESTCONF regression: https://jira.opendaylight.org/browse/NETCONF-834

I have the fix and will be rolling it out as soon as possible.

Regards,
Robert

On 22/11/2021 23:11, Daniel de la Rosa wrote:

it seems that there are still BGPCEP, OVSDB and OFP issues
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/228/>

On the BGPCEP side, this seems to be a problem with in RFC8040 request URI format:

http://10.30.170.109:8181/rests/data/odl-data-change-counter-config:data-change-counter-config/data-change-counter


results it:

<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">
<error>
<error-tag>missing-attribute</error-tag>
<error-message>Entry '(urn:opendaylight:params:xml:ns:yang:bgpcep:data-change-counter-config?revision=2017-04-24)data-change-counter-config' requires key or value predicate to be present.
</error-message>
<error-type>protocol</error-type>
</error>
</errors>

I think that should read

http://10.30.170.109:8181/rests/data/odl-data-change-counter-config:data-change-counter-config=data-change-counter

instead, but let me get back to you.

Regards,
Robert

On 15/11/2021 20:22, Robert Varga wrote:

On 15/11/2021 17:54, Daniel de la Rosa wrote:

On Wed, Nov 10, 2021 at 11:36 AM Robert Varga <nite@...

The bgpcep regression (https://jira.opendaylight.org/browse/BGPCEP-988) is tricky, as it seems we turned around a rock under which it was hiding for couple of years.
Nevertheless I think we have a pretty good idea as to what is going on and should be able to clear that in the next few days.
Anyway, I am rolling out an update to get the things we have now into wider testing.

Alright, so BGPCEP-988 is confirmed passing in a Sulfur, thanks to Marek and Olivier for tracking it down and fixing it.

With bgpcep-0.16.11 we are back to passing completely here: https://jenkins.opendaylight.org/releng/view/autorelease/job/bgpcep-csit-1node-userfeatures-all-sulfur/

The corresponding Phosphorus job's manual runs seem to be mismatching on distro name somehow, but the next AR should be fine AFAICT.

Regards,
Robert

On 19/11/2021 06:27, Richard Kosegi wrote:

Hi,
I removed references to prefix-shard module in daexim's tests https://git.opendaylight.org/gerrit/c/integration/test/+/98613 <https://git.opendaylight.org/gerrit/c/integration/test/+/98613>
CSIT seems to pass on sandbox https://jenkins.opendaylight.org/sandbox/view/All/job/daexim-csit-1node-basic-only-phosphorus/1/ <https://jenkins.opendaylight.org/sandbox/view/All/job/daexim-csit-1node-basic-only-phosphorus/1/>

Confirmed on Sulfur here: https://jenkins.opendaylight.org/releng/job/daexim-csit-3node-clustering-basic-only-sulfur/

Thanks,
Robert

Regards,
Richard
On Fri, 19 Nov 2021 at 00:57, Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
On Thu, Nov 18, 2021 at 10:38 AM Robert Varga <nite@...
<mailto:nite@...>> wrote:
On 18/11/2021 19:28, Richard Kosegi wrote:
> Hi Daniel,
>
> I don't think this has anything to do with daexim, it can't
import data
> into an operational datastore because the offending module
> (shard-prefix) is not loaded.
> The Module seems to belong to controller IIRC:
>
> Schema node with name prefix-shards was not found under
(urn:ietf:params:xml:ns:netconf:base:1.0)data
Right, but prefix shards have been removed in
https://jira.opendaylight.org/browse/CONTROLLER-1977
<https://jira.opendaylight.org/browse/CONTROLLER-1977>, so
daexim should
not rely on them...
Richard, is this something you can help with ?
Thanks
Regards,
Robert

>
>
> Regards,
> Richard.
>
>
> On Thu, 18 Nov 2021 at 17:15, Daniel de la Rosa
<ddelarosa0707@... <mailto:ddelarosa0707@...>
> <mailto:ddelarosa0707@...
<mailto:ddelarosa0707@...>>> wrote:
>
>     Thanks Robert and all... Richard, we are having some
issues with
>     Daexim, is that something you can help with?
>
>
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>
>
>     On Mon, Nov 15, 2021 at 11:22 AM Robert Varga <nite@...
<mailto:nite@...>
>     <mailto:nite@... <mailto:nite@...>>> wrote:
>
>         On 15/11/2021 17:54, Daniel de la Rosa wrote:
>          >
>          >
>          > On Wed, Nov 10, 2021 at 11:36 AM Robert Varga
<nite@... <mailto:nite@...>
>         <mailto:nite@... <mailto:nite@...>>
>          > <mailto:nite@... <mailto:nite@...>
<mailto:nite@... <mailto:nite@...>>>> wrote:
>          >
>          >     On 10/11/2021 06:54, Daniel de la Rosa wrote:
>          >      > Hello TSC and all
>          >      >
>          >      > It looks like we can't pick a phosphorus RC
for SR1
>         from the
>          >     failures we
>          >      > are getting
>          >      >
>          >      >
>          >
>
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>
>          >
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>>
>          >
>          >      >
>          >
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>
>          >
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/> <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>>>
>          >      >
>          >      > Please let me know if there are fixes in
progress for
>         these issues
>          >
>          >     I am currently tracking two issues in
controller and one
>         in bgpcep we
>          >     want to ship in SR1.
>          >
>          >
>          > Thanks Robert. Hopefully the issues can be
resolved this week.
>
>         We are done with the controller things (thanks
Tomas), with
>         actually
>         some unreported bugs being shaken out as well.
>
>         The bgpcep regression
>         (https://jira.opendaylight.org/browse/BGPCEP-988
<https://jira.opendaylight.org/browse/BGPCEP-988>
>         <https://jira.opendaylight.org/browse/BGPCEP-988
<https://jira.opendaylight.org/browse/BGPCEP-988>>)
>         is tricky, as it seems we turned around a rock under
which it
>         was hiding
>         for couple of years.
>
>         Nevertheless I think we have a pretty good idea as to
what is
>         going on
>         and should be able to clear that in the next few days.
>
>         Anyway, I am rolling out an update to get the things
we have now
>         into
>         wider testing.
>
>         Regards,
>         Robert
>
>
--
Daniel de la Rosa
ODL Release Manager

On 18/11/2021 19:36, Daniel de la Rosa wrote:

Ok, thanks for the clarification.. so @Robert Varga <mailto:nite@...> this is not part of the controller tickets that you and @Tomáš Cére <mailto:tomas.cere@...>  are working on?
CONTROLLER-2025 <https://jira.opendaylight.org/browse/CONTROLLER-2025> and CONTROLLER-2026 <https://jira.opendaylight.org/browse/CONTROLLER-2026> right?

Nope, those two are related to the new EOS implementation.

Regards,
Robert

On 18/11/2021 19:28, Richard Kosegi wrote:

Hi Daniel,
I don't think this has anything to do with daexim, it can't import data into an operational datastore because the offending module (shard-prefix) is not loaded.
The Module seems to belong to controller IIRC:
Schema node with name prefix-shards was not found under (urn:ietf:params:xml:ns:netconf:base:1.0)data

Right, but prefix shards have been removed in https://jira.opendaylight.org/browse/CONTROLLER-1977, so daexim should not rely on them...

Regards,
Robert

Regards,
Richard.
On Thu, 18 Nov 2021 at 17:15, Daniel de la Rosa <ddelarosa0707@... <mailto:ddelarosa0707@...>> wrote:
Thanks Robert and all... Richard, we are having some issues with
Daexim, is that something you can help with?
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>
On Mon, Nov 15, 2021 at 11:22 AM Robert Varga <nite@...
<mailto:nite@...>> wrote:
On 15/11/2021 17:54, Daniel de la Rosa wrote:
>
>
> On Wed, Nov 10, 2021 at 11:36 AM Robert Varga <nite@...
<mailto:nite@...>
> <mailto:nite@... <mailto:nite@...>>> wrote:
>
>     On 10/11/2021 06:54, Daniel de la Rosa wrote:
>      > Hello TSC and all
>      >
>      > It looks like we can't pick a phosphorus RC for SR1
from the
>     failures we
>      > are getting
>      >
>      >
>
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>
>
>      >
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>
>
 <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/ <https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>>
>      >
>      > Please let me know if there are fixes in progress for
these issues
>
>     I am currently tracking two issues in controller and one
in bgpcep we
>     want to ship in SR1.
>
>
> Thanks Robert. Hopefully the issues can be resolved this week.
We are done with the controller things (thanks Tomas), with
actually
some unreported bugs being shaken out as well.
The bgpcep regression
(https://jira.opendaylight.org/browse/BGPCEP-988
<https://jira.opendaylight.org/browse/BGPCEP-988>)
is tricky, as it seems we turned around a rock under which it
was hiding
for couple of years.
Nevertheless I think we have a pretty good idea as to what is
going on
and should be able to clear that in the next few days.
Anyway, I am rolling out an update to get the things we have now
into
wider testing.
Regards,
Robert

On 17/11/2021 17:42, Ha, Sangwook wrote:

Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together?

Yes there is and there is quite a bit of history attached to that.

Our governance clearly states that each project is independent, which in this context means is free to release whenever as well as can decide to release outside of Simultaneous Release.

During our initial (Hydrogen, 2014) release, we have had all projects integrating on SNAPSHOTs and the release party was ... not awesome. If you see git tags like "jenkins-controller-bulk-release-prepare-only-2-1", those are from that period. There were multiple technical reasons why it did not go so well.

As a reaction to that, autorelease was created, to have all projects still integrated on SNAPSHOTs, but projects gave up their right to release on their own and instead all projects were release by LFN personnel in one large chunk -- we are still doing this for MSI projects.

The experience of being integrated on SNAPSHOTs was ... not exactly great -- it lead to the creation of validate-autorelease and distribution-check jobs, which gate every patch so that it does not happen to break downstreams.

We have mostly addressed the technical issues by 2017 and started peeling projects away from autorelease with odlparent-2.0.0 (IIRC). Fast forward to today and autorelease does not carry a single kernel project.

With that context, I will never agree to going for "release together" --
that amounts to autorelease hell. I have endured it for years upon years and have toiled sweat and blood to get out of it. I am *NEVER* going back to that, period.


Can we do better than we are doing today?

Certainly.

There are multiple reasons why kernel project releases happen "a few days apart". It is mostly a manual process and you can probably guess whose time is being spent on it.

There is silver lining, though, as Nexus promotions take ~30 minutes for most projects, not 2+ hours like they used to just two months ago. Now if we only had reliable automation taking advantage of that...

Regards,
Robert

_________________________________________________________________________________________________________________________

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.

On 15/11/2021 17:54, Daniel de la Rosa wrote:

On Wed, Nov 10, 2021 at 11:36 AM Robert Varga <nite@... <mailto:nite@...>> wrote:
On 10/11/2021 06:54, Daniel de la Rosa wrote:
> Hello TSC and all
>
> It looks like we can't pick a phosphorus RC for SR1 from the
failures we
> are getting
>
>
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>

>
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/
<https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-phosphorus/>>
>
> Please let me know if there are fixes in progress for these issues
I am currently tracking two issues in controller and one in bgpcep we
want to ship in SR1.
Thanks Robert. Hopefully the issues can be resolved this week.

We are done with the controller things (thanks Tomas), with actually some unreported bugs being shaken out as well.

The bgpcep regression (https://jira.opendaylight.org/browse/BGPCEP-988) is tricky, as it seems we turned around a rock under which it was hiding for couple of years.

Nevertheless I think we have a pretty good idea as to what is going on and should be able to clear that in the next few days.

Anyway, I am rolling out an update to get the things we have now into wider testing.

Regards,
Robert