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. 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. 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? 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 > node-docker-full-deploy-all-carbon/390/log.html.gz#s1-s1-s1 > > > Thanks, > JamO > _______________________________________________ > sfc-dev mailing list > sfc-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/sfc-dev > _______________________________________________ sfc-dev mailing list sfc-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/sfc-dev
