horizon service not running or not detected by python-tempestconf

[wes hayutin]

https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_163/731357/1/check/puppet-horizon-tripleo-standalone/1635cbb/logs/undercloud/home/zuul/tempest/tempest.log

should see weshay|ruck> 2020-05-29 02:16:20.003 230667 INFO tempest.test_discover.plugins [-] Loading tests from Tempest plugin: horizon

like in working version of the job:
https://80cd7359a330b8308cec-4db038fcb6d2aaec6902b77d2fb6be2d.ssl.cf2.rackcdn.com/731633/1/check/puppet-horizon-tripleo-standalone/abbe95c/logs/undercloud/home/zuul/tempest/tempest.log

Several failed builds
https://zuul.openstack.org/builds?job_name=puppet-horizon-tripleo-standalone

If we can confirm the service did not come up in horizon.. CI did the right thing.
If python-tempestconfig failed in discovery.. it's CI's issue.

Some errors in the horizon log
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_163/731357/1/check/puppet-horizon-tripleo-standalone/1635cbb/logs/undercloud/var/log/extra/podman/containers/horizon/stdout.log

[wes hayutin (weshayutin)]

Having two tempest tests defined, would the ignore the issue if horizon was not discovered..
We perhaps do not want this
https://review.opendev.org/733381

[Alex Schultz (alex-schultz)]

The service was running according to podman

[Takashi Kajinami (kajinamit)]

Is it correct that this bug is for the failure detected in stable/train puppet-horizon-tripleo-standalone >

I've investigated the issue, but seems like horizon_tempest package is missing from director,
and guess something has been changed in os-tempest or package dependencies.

[Marios Andreou (marios-b)]

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo