On 12/22/2017 07:45 AM, Sam Hague wrote:
> 
> 
> On Fri, Dec 22, 2017 at 7:37 AM, Jaime Caamaño Ruiz <jcaam...@suse.de 
> <mailto:jcaam...@suse.de>> wrote:
> 
>     Hello Jamo
> 
>     Took a quick look.
> 
>     The problem seems to be that the odl-sfc-openflow-renderer feature is
>     installed but the dependant bundles are not activated. This feature is
>     in charge of writing the flows, and the test fails because there are no
>     flows on the  switches.

yeah, I saw a bunch of ugly karaf.log messages as well. There is an NPE showing
up from sfc code that may or may not be important. Check this log:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sfc-csit-3node-docker-full-deploy-all-carbon/390/odl1_karaf.log.gz

>     This is not the only feature with this problem, seems to me than more
>     than one bundle is just not properly started. So something is wrong in
>     the feature or blueprint handling. Unfortunately, older logs are not
>     available to compare but there were no changes in Carbon since the last
>     success job.

I tried a job with Carbon SR2 since that should probably have been from
before when it was passing. It failed as well. The logs didn't save, but
you can see in the console log that it's the same failure:

https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-csit-3node-docker-full-deploy-all-carbon/392/console

Thanks,
JamO


>     Oxygen job is also failing from Dec 9. On this case, seems that there
>     is no connectivity between the docker network running in the tools
>     system and ODL. Something that we fixed few days ago caused by a new
>     tools docker image that did not have ip forward enabled. But now I dont
>     know what is the problem. When did we effectively switch to new cloud
>     provider?
> 
> the switch was last week so around the 15th. 
> 
> 
>     BR
>     Jaime.
> 
> 
>     On Thu, 2017-12-21 at 16:57 -0800, Jamo Luhrsen wrote:
>     > Hi SFC,
>     >
>     > I can't remember if there was ever any discussion on this one yet,
>     > but there is a
>     > consistent failure it would be nice to see fixed. Or if there is a
>     > low sev bug
>     > we can point to, I'll edit the test to list that bug in the report.
>     >
>     > looks like there is something not showing up in an ovs docker
>     > containers flow
>     > table. Specifically, it's not finding "*actions=pop_nsh*"
>     >
>     > I'm vaguely remembering something regarding this, but can't recall it
>     > exactly.
>     >
>     > here's an example:
>     > https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sfc-csit-3
>     <https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sfc-csit-3>
>     > node-docker-full-deploy-all-carbon/390/log.html.gz#s1-s1-s1
>     >
>     >
>     > Thanks,
>     > JamO
>     > _______________________________________________
>     > sfc-dev mailing list
>     > sfc-dev@lists.opendaylight.org <mailto:sfc-dev@lists.opendaylight.org>
>     > https://lists.opendaylight.org/mailman/listinfo/sfc-dev 
> <https://lists.opendaylight.org/mailman/listinfo/sfc-dev>
>     >
>     _______________________________________________
>     integration-dev mailing list
>     integration-...@lists.opendaylight.org 
> <mailto:integration-...@lists.opendaylight.org>
>     https://lists.opendaylight.org/mailman/listinfo/integration-dev
>     <https://lists.opendaylight.org/mailman/listinfo/integration-dev>
> 
> 
_______________________________________________
sfc-dev mailing list
sfc-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to