date:20170109

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Mainzer, Gal

Maybe not as a gate job but more of a periodic that runs every 4-6 hours.

At this stage, those jobs are stable enough (and if not we are really close to 
that point) for a single failure to state that there is a regression. All we 
need to agree is that if that cloud suite is failing - all relevant project 
should stop merging (even as a process and not by a gerrit mechanic lock) until 
we are back from regression.

We can add additional job that with a single click, will collect all commits 
from all relevant projects that are suspected - as Jamo said, ~15 are 
dependent. This will reduce our analysis time by even maybe reverting suspected 
commits just to come back from the regression and release the "lock".

Without proper dashboard I'm not really expecting all projects to monitor this, 
but at first stage we can monitor that job (like we do today) and send critical 
mail on certain failures.

Sent from my iPhone

On 10 Jan 2017, at 1:31, Robert Varga  wrote:

> On 01/09/2017 10:37 PM, Jamo Luhrsen wrote:
> so you mean to have this "cloud suite" run as a gating job on gerrit patches 
> for all projects that
> our "ODL for openstack" needs, I think. That would be nice, but we would need 
> to convince a lot of
> projects to do it. Looks like at least 12 projects are dependencies for 
> netvirt:
> 
> controller,dlux,genius,infrautils,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,yangtools

Judging from how long it takes for -autorelease and -distcheck to
stabilize for each release, I would hate to see such a job gate offset-0
patches.

In this particular set of projects, there is a history of breakage
happening on OFP/OVSDB and OVSDB/SFC (I think) boundaries.

Just my .02,
Robert

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Jamo Luhrsen



On 01/09/2017 01:03 PM, Mainzer, Gal wrote:
> Mis-fired the mail early.
> 
> Looking at this fast analysis done by the whole community, won't it be a good 
> idea to maybe have some kind of "ODL cloud
> sanity" suite that will keep all projects affecting ODL for openstack in a 
> non breaking state?

so you mean to have this "cloud suite" run as a gating job on gerrit patches 
for all projects that
our "ODL for openstack" needs, I think. That would be nice, but we would need 
to convince a lot of
projects to do it. Looks like at least 12 projects are dependencies for netvirt:

controller,dlux,genius,infrautils,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,yangtools

that's taken from here:
https://logs.opendaylight.org/releng/jenkins092/autorelease-release-carbon/119/archives/dependencies.log.gz


JamO



> I'm sure there are other use cases that can add more similar ODL suites.
> 
> Sent from my iPhone
> 
> On 9 Jan 2017, at 22:57, Mainzer, Gal  wrote:
> 
> Issue affect found by us and reported to community, which after couple of 
> hours was pin pointed by the community.
> 
> Sanity/hourly concepts are still mainly pushed by us (Alon, Koby and ravit) 
> but once we find something, community helps
> with the fast analysis (at least here).
> 
> Sent from my iPhone
> 
> On 9 Jan 2017, at 22:45, Luis Gomez  wrote:
> 
> I like to code note idea but I think there could be also people running their 
> own tools to deploy cluster so any change in
> the cluster configuration is good to broadcast IMHO.
> 
> 
>> On Jan 9, 2017, at 11:24 AM, Vratko Polak -X (vrpolak - PANTHEON 
>> TECHNOLOGIES at Cisco)  wrote:
>> 
>> When you have a tight coupling like this, general terms such as "controller 
>> people" or "the community" rarely achieve
>> the desired focus.
>> 
>> I prefer such notes to be as close to the code as possible. 
>> https://git.opendaylight.org/gerrit/#/c/50140/1/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf
>>
>>
>> 
Vratko.
>> 
>> -Original Message- From: 
>> controller-dev-boun...@lists.opendaylight.org
>> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Luis 
>> Gomez Sent: 9 January, 2017 18:13 To:
>> controller-dev@lists.opendaylight.org Cc: 
>> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
>> Kochba,
>> Alon ; mdsal-...@lists.opendaylight.org; 
>> integration-...@lists.opendaylight.org; Peretz, Ravit
>> ; Aizer, Koby  Subject: Re: 
>> [controller-dev] [mdsal-dev] 3node cluster
>> regression in Carbon - since Jan 5th
>> 
>> Patch looks good but in future I would ask controller people to inform 
>> broadly the community when you do these changes
>> specially if they impact the cluster configuration.
>> 
>> BR/Luis
>> 
>> 
>>> On Jan 9, 2017, at 5:28 AM, Peretz, Ravit  wrote:
>>> 
>>> CSIT uses configure_cluster.sh to configure 3node jobs which creates 
>>> akka.conf with akka.tcp instead of akka.
>>> 
>>> Please review my fix patch: https://git.opendaylight.org/gerrit/50129
>>> 
>>> Thanks, Ravit.
>>> 
>>> -Original Message- From: Tomas Cere -X (tcere - PANTHEON 
>>> TECHNOLOGIES at Cisco) [mailto:tc...@cisco.com] Sent:
>>> יום ב 09 ינואר 2017 15:00 To: Robert Varga ; Peretz, Ravit 
>>> ; 
>>> integration-...@lists.opendaylight.org; netvirt-...@lists.opendaylight.org; 
>>> genius-...@lists.opendaylight.org; 
>>> controller-dev@lists.opendaylight.org; mdsal-...@lists.opendaylight.org Cc: 
>>> Aizer, Koby ; Kochba,
>>> Alon  Subject: RE: [controller-dev] [mdsal-dev] 3node 
>>> cluster regression in Carbon - since Jan 5th
>>> 
>>> It's already tracked by : 
>>> https://bugs.opendaylight.org/show_bug.cgi?id=7493 I suspect it's the tests 
>>> providing their
>>> own akka.conf which does not have the artery setup included.
>>> 
>>> Tomas
>>> 
>>> -Original Message- From: 
>>> controller-dev-boun...@lists.opendaylight.org 
>>> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Robert 
>>> Varga Sent: Monday, January 09, 2017 13:59 
>>> To: Peretz, Ravit ; 
>>> integration-...@lists.opendaylight.org; netvirt-...@lists.opendaylight.org;
>>> genius-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org; 
>>> mdsal-...@lists.opendaylight.org Cc: Aizer,
>>> Koby ; Kochba, Alon  Subject: Re: 
>>> [controller-dev] [mdsal-dev] 3node cluster
>>> regression in Carbon - since Jan 5th
>>> 
>>> 
>>> 
 On 01/09/2017 01:53 PM, Peretz, Ravit wrote: Hi all,
 
 
 
 It seems like there is a massive 3node cluster regression in carbon, since 
 approximately 21:0PM January 5^th .
 
 We can see that many 3node CSIT fails across projects.
 
 
 
 After a quick look Koby and I have

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Mainzer, Gal

Mis-fired the mail early.

Looking at this fast analysis done by the whole community, won't it be a good 
idea to maybe have some kind of "ODL cloud sanity" suite that will keep all 
projects affecting ODL for openstack in a non breaking state?

I'm sure there are other use cases that can add more similar ODL suites.

Sent from my iPhone

On 9 Jan 2017, at 22:57, Mainzer, Gal  wrote:

Issue affect found by us and reported to community, which after couple of hours 
was pin pointed by the community.

Sanity/hourly concepts are still mainly pushed by us (Alon, Koby and ravit) but 
once we find something, community helps with the fast analysis (at least here).

Sent from my iPhone

On 9 Jan 2017, at 22:45, Luis Gomez  wrote:

I like to code note idea but I think there could be also people running their 
own tools to deploy cluster so any change in the cluster configuration is good 
to broadcast IMHO.


> On Jan 9, 2017, at 11:24 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES 
> at Cisco)  wrote:
> 
> When you have a tight coupling like this,
> general terms such as "controller people" or "the community"
> rarely achieve the desired focus.
> 
> I prefer such notes to be as close to the code as possible.
> https://git.opendaylight.org/gerrit/#/c/50140/1/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf
> 
> Vratko.
> 
> -Original Message-
> From: controller-dev-boun...@lists.opendaylight.org 
> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Luis Gomez
> Sent: 9 January, 2017 18:13
> To: controller-dev@lists.opendaylight.org
> Cc: netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
> Kochba, Alon ; mdsal-...@lists.opendaylight.org; 
> integration-...@lists.opendaylight.org; Peretz, Ravit ; 
> Aizer, Koby 
> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon 
> - since Jan 5th
> 
> Patch looks good but in future I would ask controller people to inform 
> broadly the community when you do these changes specially if they impact the 
> cluster configuration.
> 
> BR/Luis
> 
> 
>> On Jan 9, 2017, at 5:28 AM, Peretz, Ravit  wrote:
>> 
>> CSIT uses configure_cluster.sh to configure 3node jobs which creates 
>> akka.conf with akka.tcp instead of akka.
>> 
>> Please review my fix patch:
>> https://git.opendaylight.org/gerrit/50129
>> 
>> Thanks,
>> Ravit.
>> 
>> -Original Message-
>> From: Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
>> [mailto:tc...@cisco.com]
>> Sent: יום ב 09 ינואר 2017 15:00
>> To: Robert Varga ; Peretz, Ravit ; 
>> integration-...@lists.opendaylight.org; 
>> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
>> controller-dev@lists.opendaylight.org; 
>> mdsal-...@lists.opendaylight.org
>> Cc: Aizer, Koby ; Kochba, Alon 
>> Subject: RE: [controller-dev] [mdsal-dev] 3node cluster regression in 
>> Carbon - since Jan 5th
>> 
>> It's already tracked by : 
>> https://bugs.opendaylight.org/show_bug.cgi?id=7493
>> I suspect it's the tests providing their own akka.conf which does not have 
>> the artery setup included.
>> 
>> Tomas
>> 
>> -Original Message-
>> From: controller-dev-boun...@lists.opendaylight.org 
>> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of 
>> Robert Varga
>> Sent: Monday, January 09, 2017 13:59
>> To: Peretz, Ravit ; 
>> integration-...@lists.opendaylight.org; 
>> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
>> controller-dev@lists.opendaylight.org; 
>> mdsal-...@lists.opendaylight.org
>> Cc: Aizer, Koby ; Kochba, Alon 
>> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in 
>> Carbon - since Jan 5th
>> 
>> 
>> 
>>> On 01/09/2017 01:53 PM, Peretz, Ravit wrote:
>>> Hi all,
>>> 
>>> 
>>> 
>>> It seems like there is a massive 3node cluster regression in carbon, 
>>> since approximately 21:0PM January 5^th .
>>> 
>>> We can see that many 3node CSIT fails across projects.
>>> 
>>> 
>>> 
>>> After a quick look Koby and I have found what we assume is the faulty 
>>> zip.  We looked at the last successful openflowplugin-3 node run:
>>> 
>>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>>> n ode-clustering-only-carbon/379/console.log.gz
>>> 
>>> which used distribution: 0.6.0-20170105.205720-2879.zip
>>> 
>>> 
>>> 
>>> the next run failed, with the same error we are seeing now in all 
>>> runs (at least the few we checked):
>>> 
>>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>>> n ode-clustering-only-carbon/380/console.log.gz
>>> 
>>> which used distribution: 0.6.0-20170105.235121-2883.zip
>>> 
>>> 
>>> 
>>> 
>>> 
>>> we were able to narrow it down to a single

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Luis Gomez

I like to code note idea but I think there could be also people running their 
own tools to deploy cluster so any change in the cluster configuration is good 
to broadcast IMHO.


> On Jan 9, 2017, at 11:24 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES 
> at Cisco)  wrote:
> 
> When you have a tight coupling like this,
> general terms such as "controller people" or "the community"
> rarely achieve the desired focus.
> 
> I prefer such notes to be as close to the code as possible.
> https://git.opendaylight.org/gerrit/#/c/50140/1/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf
> 
> Vratko.
> 
> -Original Message-
> From: controller-dev-boun...@lists.opendaylight.org 
> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Luis Gomez
> Sent: 9 January, 2017 18:13
> To: controller-dev@lists.opendaylight.org
> Cc: netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
> Kochba, Alon ; mdsal-...@lists.opendaylight.org; 
> integration-...@lists.opendaylight.org; Peretz, Ravit ; 
> Aizer, Koby 
> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon 
> - since Jan 5th
> 
> Patch looks good but in future I would ask controller people to inform 
> broadly the community when you do these changes specially if they impact the 
> cluster configuration.
> 
> BR/Luis
> 
> 
>> On Jan 9, 2017, at 5:28 AM, Peretz, Ravit  wrote:
>> 
>> CSIT uses configure_cluster.sh to configure 3node jobs which creates 
>> akka.conf with akka.tcp instead of akka.
>> 
>> Please review my fix patch:
>> https://git.opendaylight.org/gerrit/50129
>> 
>> Thanks,
>> Ravit.
>> 
>> -Original Message-
>> From: Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
>> [mailto:tc...@cisco.com]
>> Sent: יום ב 09 ינואר 2017 15:00
>> To: Robert Varga ; Peretz, Ravit ; 
>> integration-...@lists.opendaylight.org; 
>> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
>> controller-dev@lists.opendaylight.org; 
>> mdsal-...@lists.opendaylight.org
>> Cc: Aizer, Koby ; Kochba, Alon 
>> Subject: RE: [controller-dev] [mdsal-dev] 3node cluster regression in 
>> Carbon - since Jan 5th
>> 
>> It's already tracked by : 
>> https://bugs.opendaylight.org/show_bug.cgi?id=7493
>> I suspect it's the tests providing their own akka.conf which does not have 
>> the artery setup included.
>> 
>> Tomas
>> 
>> -Original Message-
>> From: controller-dev-boun...@lists.opendaylight.org 
>> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of 
>> Robert Varga
>> Sent: Monday, January 09, 2017 13:59
>> To: Peretz, Ravit ; 
>> integration-...@lists.opendaylight.org; 
>> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
>> controller-dev@lists.opendaylight.org; 
>> mdsal-...@lists.opendaylight.org
>> Cc: Aizer, Koby ; Kochba, Alon 
>> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in 
>> Carbon - since Jan 5th
>> 
>> 
>> 
>> On 01/09/2017 01:53 PM, Peretz, Ravit wrote:
>>> Hi all,
>>> 
>>> 
>>> 
>>> It seems like there is a massive 3node cluster regression in carbon, 
>>> since approximately 21:0PM January 5^th .
>>> 
>>> We can see that many 3node CSIT fails across projects.
>>> 
>>> 
>>> 
>>> After a quick look Koby and I have found what we assume is the faulty 
>>> zip.  We looked at the last successful openflowplugin-3 node run:
>>> 
>>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>>> n ode-clustering-only-carbon/379/console.log.gz
>>> 
>>> which used distribution: 0.6.0-20170105.205720-2879.zip
>>> 
>>> 
>>> 
>>> the next run failed, with the same error we are seeing now in all 
>>> runs (at least the few we checked):
>>> 
>>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>>> n ode-clustering-only-carbon/380/console.log.gz
>>> 
>>> which used distribution: 0.6.0-20170105.235121-2883.zip
>>> 
>>> 
>>> 
>>> 
>>> 
>>> we were able to narrow it down to a single distribution that was the 
>>> first to fail:
>>> 
>>> https://logs.opendaylight.org/releng/jenkins092/netvirt-legacy-csit-3
>>> n ode-clustering-only-carbon/144/console.log.gz
>>> 
>>> 0.6.0-20170105.222635-2880.zip
>>> 
>>> 
>>> 
>>> *We would appreciate your help with narrowing down the faulty 
>>> commit/s triggering the 0.6.0-20170105.222635-2880.zip distribution.*
>>> 
>>> 
>>> 
>>> 
>>> 
>>> The first error we saw in the logs is :
>>> 2017-01-06 05:25:30,158 | ERROR | lt-dispatcher-12 |
>>> ClusterActorRefProvider  | 199 - com.typesafe.akka.slf4j -
>>> 2.4.16 | No root guardian at
>>> [akka.tcp://opendaylight-cluster-data@10.29.13.119:2550]
>>> 
>>> java.lang.IllegalArgumentException: Wrong protocol of 
>>>

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)

When you have a tight coupling like this,
general terms such as "controller people" or "the community"
rarely achieve the desired focus.

I prefer such notes to be as close to the code as possible.
https://git.opendaylight.org/gerrit/#/c/50140/1/opendaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf

Vratko.

-Original Message-
From: controller-dev-boun...@lists.opendaylight.org 
[mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Luis Gomez
Sent: 9 January, 2017 18:13
To: controller-dev@lists.opendaylight.org
Cc: netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
Kochba, Alon ; mdsal-...@lists.opendaylight.org; 
integration-...@lists.opendaylight.org; Peretz, Ravit ; 
Aizer, Koby 
Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - 
since Jan 5th

Patch looks good but in future I would ask controller people to inform broadly 
the community when you do these changes specially if they impact the cluster 
configuration.

BR/Luis


> On Jan 9, 2017, at 5:28 AM, Peretz, Ravit  wrote:
> 
> CSIT uses configure_cluster.sh to configure 3node jobs which creates 
> akka.conf with akka.tcp instead of akka.
> 
> Please review my fix patch:
> https://git.opendaylight.org/gerrit/50129
> 
> Thanks,
> Ravit.
> 
> -Original Message-
> From: Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
> [mailto:tc...@cisco.com]
> Sent: יום ב 09 ינואר 2017 15:00
> To: Robert Varga ; Peretz, Ravit ; 
> integration-...@lists.opendaylight.org; 
> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
> controller-dev@lists.opendaylight.org; 
> mdsal-...@lists.opendaylight.org
> Cc: Aizer, Koby ; Kochba, Alon 
> Subject: RE: [controller-dev] [mdsal-dev] 3node cluster regression in 
> Carbon - since Jan 5th
> 
> It's already tracked by : 
> https://bugs.opendaylight.org/show_bug.cgi?id=7493
> I suspect it's the tests providing their own akka.conf which does not have 
> the artery setup included.
> 
> Tomas
> 
> -Original Message-
> From: controller-dev-boun...@lists.opendaylight.org 
> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of 
> Robert Varga
> Sent: Monday, January 09, 2017 13:59
> To: Peretz, Ravit ; 
> integration-...@lists.opendaylight.org; 
> netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; 
> controller-dev@lists.opendaylight.org; 
> mdsal-...@lists.opendaylight.org
> Cc: Aizer, Koby ; Kochba, Alon 
> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in 
> Carbon - since Jan 5th
> 
> 
> 
> On 01/09/2017 01:53 PM, Peretz, Ravit wrote:
>> Hi all,
>> 
>> 
>> 
>> It seems like there is a massive 3node cluster regression in carbon, 
>> since approximately 21:0PM January 5^th .
>> 
>> We can see that many 3node CSIT fails across projects.
>> 
>> 
>> 
>> After a quick look Koby and I have found what we assume is the faulty 
>> zip.  We looked at the last successful openflowplugin-3 node run:
>> 
>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>> n ode-clustering-only-carbon/379/console.log.gz
>> 
>> which used distribution: 0.6.0-20170105.205720-2879.zip
>> 
>> 
>> 
>> the next run failed, with the same error we are seeing now in all 
>> runs (at least the few we checked):
>> 
>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3
>> n ode-clustering-only-carbon/380/console.log.gz
>> 
>> which used distribution: 0.6.0-20170105.235121-2883.zip
>> 
>> 
>> 
>> 
>> 
>> we were able to narrow it down to a single distribution that was the 
>> first to fail:
>> 
>> https://logs.opendaylight.org/releng/jenkins092/netvirt-legacy-csit-3
>> n ode-clustering-only-carbon/144/console.log.gz
>> 
>> 0.6.0-20170105.222635-2880.zip
>> 
>> 
>> 
>> *We would appreciate your help with narrowing down the faulty 
>> commit/s triggering the 0.6.0-20170105.222635-2880.zip distribution.*
>> 
>> 
>> 
>> 
>> 
>> The first error we saw in the logs is :
>> 2017-01-06 05:25:30,158 | ERROR | lt-dispatcher-12 |
>> ClusterActorRefProvider  | 199 - com.typesafe.akka.slf4j -
>> 2.4.16 | No root guardian at
>> [akka.tcp://opendaylight-cluster-data@10.29.13.119:2550]
>> 
>> java.lang.IllegalArgumentException: Wrong protocol of 
>> [akka.tcp://opendaylight-cluster-data@10.29.13.119:2550/], expected 
>> [akka]
> 
> Looks like mismatch in setup, this is related to akka artery -- the protocol 
> should be akka, not akka.tcp. Where is this configuration coming from?
> 
> Regards,
> Robert
> ___
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev
> ___
>

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

2017-01-09 Thread Luis Gomez

Patch looks good but in future I would ask controller people to inform broadly 
the community when you do these changes specially if they impact the cluster 
configuration.

BR/Luis


> On Jan 9, 2017, at 5:28 AM, Peretz, Ravit  wrote:
> 
> CSIT uses configure_cluster.sh to configure 3node jobs which creates 
> akka.conf with akka.tcp instead of akka.
> 
> Please review my fix patch:
> https://git.opendaylight.org/gerrit/50129
> 
> Thanks,
> Ravit.
> 
> -Original Message-
> From: Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
> [mailto:tc...@cisco.com] 
> Sent: יום ב 09 ינואר 2017 15:00
> To: Robert Varga ; Peretz, Ravit ; 
> integration-...@lists.opendaylight.org; netvirt-...@lists.opendaylight.org; 
> genius-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org; 
> mdsal-...@lists.opendaylight.org
> Cc: Aizer, Koby ; Kochba, Alon 
> Subject: RE: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon 
> - since Jan 5th
> 
> It's already tracked by : https://bugs.opendaylight.org/show_bug.cgi?id=7493
> I suspect it's the tests providing their own akka.conf which does not have 
> the artery setup included.
> 
> Tomas
> 
> -Original Message-
> From: controller-dev-boun...@lists.opendaylight.org 
> [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Robert 
> Varga
> Sent: Monday, January 09, 2017 13:59
> To: Peretz, Ravit ; 
> integration-...@lists.opendaylight.org; netvirt-...@lists.opendaylight.org; 
> genius-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org; 
> mdsal-...@lists.opendaylight.org
> Cc: Aizer, Koby ; Kochba, Alon 
> Subject: Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon 
> - since Jan 5th
> 
> 
> 
> On 01/09/2017 01:53 PM, Peretz, Ravit wrote:
>> Hi all,
>> 
>> 
>> 
>> It seems like there is a massive 3node cluster regression in carbon, 
>> since approximately 21:0PM January 5^th .
>> 
>> We can see that many 3node CSIT fails across projects.
>> 
>> 
>> 
>> After a quick look Koby and I have found what we assume is the faulty 
>> zip.  We looked at the last successful openflowplugin-3 node run:
>> 
>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3n
>> ode-clustering-only-carbon/379/console.log.gz
>> 
>> which used distribution: 0.6.0-20170105.205720-2879.zip
>> 
>> 
>> 
>> the next run failed, with the same error we are seeing now in all runs 
>> (at least the few we checked):
>> 
>> https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3n
>> ode-clustering-only-carbon/380/console.log.gz
>> 
>> which used distribution: 0.6.0-20170105.235121-2883.zip
>> 
>> 
>> 
>> 
>> 
>> we were able to narrow it down to a single distribution that was the 
>> first to fail:
>> 
>> https://logs.opendaylight.org/releng/jenkins092/netvirt-legacy-csit-3n
>> ode-clustering-only-carbon/144/console.log.gz
>> 
>> 0.6.0-20170105.222635-2880.zip
>> 
>> 
>> 
>> *We would appreciate your help with narrowing down the faulty commit/s 
>> triggering the 0.6.0-20170105.222635-2880.zip distribution.*
>> 
>> 
>> 
>> 
>> 
>> The first error we saw in the logs is :
>> 2017-01-06 05:25:30,158 | ERROR | lt-dispatcher-12 |
>> ClusterActorRefProvider  | 199 - com.typesafe.akka.slf4j -
>> 2.4.16 | No root guardian at
>> [akka.tcp://opendaylight-cluster-data@10.29.13.119:2550]
>> 
>> java.lang.IllegalArgumentException: Wrong protocol of 
>> [akka.tcp://opendaylight-cluster-data@10.29.13.119:2550/], expected 
>> [akka]
> 
> Looks like mismatch in setup, this is related to akka artery -- the protocol 
> should be akka, not akka.tcp. Where is this configuration coming from?
> 
> Regards,
> Robert
> ___
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev
> ___
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Re: [controller-dev] [integration-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

6 matches

Site Navigation

Mail list logo

Footer information