Do we want to block the release because of new exceptions coming? We need
someone to see if those exceptions are an indication of some regression
in functionality between the first sodium release and this SR1 candidate.

Also, we still need someone to look at the other 3 jobs I marked as blockers
because those do look like a netvirt functionality breakage. I just don't
know if the same problem was there in the original sodium release or not.

Thanks,
JamO

On 10/27/19 11:45 PM, srinivas.rachakonda@... wrote:

Hi Daniel/Jamo,

 

I have raised the JIRA bug:

 

https://jira.opendaylight.org/browse/NETVIRT-1634: Exceptions seen during deletion of BGP RD

 

Also updated the same in the spreadsheet as blocker as its continuously failing with the same exceptions.

 

Thanks,

Srinivas

+91-9243478719

 

From: Daniel De La Rosa <ddelarosa@...>
Sent: 26 October 2019 02:49
To: Jamo Luhrsen <jluhrsen@...>
Cc: Abhinav Gupta <abhinav.gupta@...>; R M Mishra <r.m.mishra@...>; Srinivas Rachakonda <srinivas.rachakonda@...>; TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate

 

Team. Any updates on this? 

 

On Thu, Oct 24, 2019 at 8:20 AM Jamo Luhrsen <jluhrsen@...> wrote:

You also have the two dcgw jobs to figure out:


https://jenkins.opendaylight.org/releng/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-dcgw-sodium/144/
https://jenkins.opendaylight.org/releng/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-rocky-dcgw-sodium/144/

Thanks,
JamO

 

On 10/24/19 4:21 AM, Abhinav Gupta wrote:

@Srinivas, @R M Mishra: Please focus on the 3 rows JamO has already analyzed (thanks!) and pointed to as BLOCKERs.

Regards,
Abhinav

 

From: TSC@... <TSC@...> On Behalf Of JamO Luhrsen via Lists.Opendaylight.Org
Sent: Thursday, October 24, 2019 2:24 AM
To: Abhinav Gupta <abhinav.gupta@...>; Daniel De La Rosa <ddelarosa@...>; Srinivas Rachakonda <srinivas.rachakonda@...>
Cc: TSC@...
Subject: Re: [OpenDaylight TSC] [integration-dev] Sodium SR1 release candidate

 

We need to get netvirt under control at this point. They have a lot of jobs,
and were never fully healthy but without maintenance they are going to create
a lot of work every release cycle.

I spent some time today going through our sodium sr1 failures and made progress
on the sheet:

https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939

there are three jobs with a basic netvirt failure that was ignored in
the original sodium release (openstack instance not getting an ip address)
which seems like a fundamental failure. The original sodium release let
it through under the assumption that it was a test code problem. I don't
think it is. I marked those as BLOCKER.

Should we mark the DCGW jobs as ignore? I don't have time to debug them
and they are saw-tooth failures and inconsistent. No idea if they are
regressions or not.

beyond netvirt, I'm following up on one openflowplugin job and once those
are understood we will only be left with netvirt to be done.

Thanks,
JamO

On 10/21/19 11:41 PM, Abhinav Gupta wrote:

Srinivas,

Please look into the CSIT jobs for failures. Please take help from Karthika if required. I’m in parallel onboarding myself with the overall Netvirt CSIT. Let’s discuss and get this moving.
I see 20 CSIT jobs for NetVirt. We may want to eliminate the unnecessary jobs as well.

 

Regards,
Abhinav

 

From: Daniel De La Rosa <ddelarosa@...>
Sent: Tuesday, October 22, 2019 1:49 AM
To: JamO Luhrsen <jluhrsen@...>; Abhinav Gupta <abhinav.gupta@...>
Cc: Release <release@...>; tsc@...; integration-dev@...; netvirt-dev@...; Bgpcep-Dev <bgpcep-dev@...>; controller-dev@...; lispflowmapping-dev@...; netconf-dev@...; openflowplugin-dev@...
Subject: Re: [integration-dev] Sodium SR1 release candidate

 

Team, 

 

Friendly reminder to review Sodium SR1 tracking sheet so we can release it on time.

 

 

https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939

 

 

 

Thanks

 

On Fri, Oct 18, 2019 at 11:28 AM JamO Luhrsen <jluhrsen@...> wrote:

In our weekly integration call we decided to use the most recent successful
Sodium autorelease build as our release candidate for SR1 which is due next
week on October 24th.

Here is the build:
https://nexus.opendaylight.org/content/repositories//autorelease-3438/org/opendaylight/integration/karaf/0.11.1/karaf-0.11.1.zip

Here is the integration-test job using that build:
https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-sodium/366/

Here is the tracking sheet we need to vet:
https://docs.google.com/spreadsheets/d/1CN-ACdIekRKMYRIuREIRALl6S8az7quAcQlRb3KeMJ8/edit?pli=1#gid=1864238939

Projects that have pending failures:
bgpcep, controller, lispflowmapping, netconf, netvirt, openflowplugin, ovsdb, yangtools

Thanks,
JamO

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13788): https://lists.opendaylight.org/g/integration-dev/message/13788
Mute This Topic: https://lists.opendaylight.org/mt/35075895/1964961
Group Owner: integration-dev+owner@...
Unsubscribe: https://lists.opendaylight.org/g/integration-dev/unsub  [ddelarosa@...]
-=-=-=-=-=-=-=-=-=-=-=-

 

--

Daniel de la Rosa
Customer Support Manager ( ODL release manager )
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120

 

 

--

Daniel de la Rosa
Customer Support Manager
Lumina Networks Inc.
e: ddelarosa@...
m:  +1 408 7728120