we had a master promotion 16th August [1]. Most of the jobs in the description have now had a green run [2], except periodic-tripleo-ci-centos-8-scenario010-standalone-network-master [3].
Not sure why [3] would still hit the bug whereas the others pass? Let's give it another run - in that buildset scen10 was the only job that did not pass [4] - trying a testproject run to see if it persists
we had a master promotion 16th August [1]. Most of the jobs in the description have now had a green run [2], except periodic- tripleo- ci-centos- 8-scenario010- standalone- network- master [3].
Not sure why [3] would still hit the bug whereas the others pass? Let's give it another run - in that buildset scen10 was the only job that did not pass [4] - trying a testproject run to see if it persists
remote: https:/ /review. rdoproject. org/r/28981 run periodic- tripleo- ci-centos- 8-scenario010- standalone- network- master
[1] http:// dashboard- ci.tripleo. org/d/QrkFP- zGz/upstream- and-rdo- promotions? orgId=1& fullscreen& panelId= 10 /review. rdoproject. org/zuul/ builds? job_name= periodic- tripleo- ci-centos- 8-multinode- 1ctlr-featurese t010-network- master& job_name= periodic- tripleo- ci-centos- 8-standalone- network- master& job_name= periodic- tripleo- ci-centos- 8-scenario007- standalone- network- master& job_name= periodic- tripleo- ci-centos- 8-scenario010- standalone- network- master /logserver. rdoproject. org/openstack- component- network/ opendev. org/openstack/ tripleo- ci/master/ periodic- tripleo- ci-centos- 8-scenario010- standalone- network- master/ d7636be/ logs/undercloud /var/log/ tempest/ stestr_ results. html.gz /review. rdoproject. org/zuul/ buildset/ 5a8fcc3e859042a 99968625fabbf66 a7
[2] https:/
[3] https:/
[4] https:/