periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train is failing - No such file or directory: '/home/zuul/tempest/etc/tempest_includelist.txt'

[Ronelle Landy]

periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train has been failing since 09/16:

https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train&skip=0

The console output shows that tempest is failing. The error in the tempest list is:

[Errno 2] No such file or directory: '/home/zuul/tempest/etc/tempest_includelist.txt'

Example logs:

https://logserver.rdoproject.org/65/31165/96/check/periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train/8d228e1/logs/undercloud/var/log/tempest/test_list.txt.gz

https://logserver.rdoproject.org/65/31165/96/check/periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train/8d228e1/

https://logserver.rdoproject.org/05/45105/2/check/periodic-tripleo-ci-centos-8-scenario010-ovn-provider-standalone-train/facf0c5/

[Jiri Podivin (jpodivin)]

The tempest role[1] hasn't changed in the past several weeks. Problem must be elsewhere.

The ... patch[2] removed tempest_whitelist from fs10.
Given the logic[3] handling includelist in the tempest role defaults, it may be that in absence of the whitelist, there is nothing to fill the file, which is never created. But that's just a conjecture.

[1]https://opendev.org/openstack/openstack-ansible-os_tempest/
[2]https://opendev.org/openstack/tripleo-quickstart/commit/d53a27411921f97e5037a4060170fd62f5bdc03b
[3]https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/defaults/main.yml#L170

[Arx Cruz (arxcruz)]

https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/858266 fix the issue, the problem was once we get rid of the whitelist on the featureset, we have to add it in the allowed list. train was an special case, and we only setup the tests properly for the check job, missing the periodic job.

[Jiri Podivin (jpodivin)]

I think this[4] might work[5] too. Provided we want to restore the seemingly intended behavior.

[4]https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/858260
[5]https://review.rdoproject.org/r/c/testproject/+/45111