|
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
|
|
|
|
|
|
Daniel de la Rosa
Great, thanks for the update.
|
|
|
Daniel de la Rosa
Hello all, any update on this? Sulfur integration test are still in bad shape
Great, thanks for the update.
|
|
|
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
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
>
>
|
|
|
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 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
|
|
|
