The tempest fix healed the breakage that was captured by this report. Having said that the stability of the DVR seems pretty good these days:
http://graphite.openstack.org/render/?from=-10days&height=500&until=now&width=1200&bgcolor=ffffff&fgcolor=000000&yMax=100&yMin=0&target=color(alias(movingAverage(asPercent(stats.zuul.pipeline.check.job .check-tempest-dsvm-neutron- dvr.FAILURE,sum(stats.zuul.pipeline.check.job.check-tempest-dsvm- neutron-dvr.{SUCCESS,FAILURE})),%2736hours%27),%20%27check-tempest-dsvm- neutron- dvr%27),%27orange%27)&target=color(alias(movingAverage(asPercent(stats.zuul.pipeline.check.job .check-tempest-dsvm-neutron- full.FAILURE,sum(stats.zuul.pipeline.check.job.check-tempest-dsvm- neutron-full.{SUCCESS,FAILURE})),%2736hours%27),%20%27check-tempest- dsvm-neutron-full%27),%27blue%27) ** No longer affects: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1381617 Title: Check for FIP status in scenario tests cause instability in neutron gate jobs Status in Tempest: Fix Released Bug description: Since this Tempest change: https://review.openstack.org/#/c/102700/ We verify that FloatingIP changes status correctly on association and dis-association. This has shown instability of the dvr tempest job: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiaXMgYXQgc3RhdHVzOiBBQ1RJVkUuIGZhaWxlZCAgdG8gcmVhY2ggc3RhdHVzOiBET1dOXCIgQU5EIGZpbGVuYW1lOlwiY29uc29sZS5odG1sXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MTMzODg5NTYxMTgsIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0= DVR is particularly affected. To manage notifications about this bug go to: https://bugs.launchpad.net/tempest/+bug/1381617/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
