Comment 8 for bug 1934994

To summarize... the original issue here was filed for the job at [1]. Based on this bug we skipped then re-added the tests with [2] since the job was back to green (was the original issue was seen just once? I only see one job log referenced in the description).

Then we started seeing the same test fail in the downstream rhos-17 job [3] and indeed the latest example is there from yesterday 22/07 [4].

I am not sure this is the same issue though.

The upstream trace is like (error)

Details: (HealthMonitorScenarioTest:test_LC_HTTP_healthmonitor_CRUD) show_loadbalancer provisioning_status updated to an invalid state of ERROR

The downstream trace is like (timeout)

Details: (HealthMonitorScenarioTest:setUpClass) show_loadbalancer provisioning_status failed to update to ACTIVE within the required time 900. Current status of show_loadbalancer: PENDING_CREATE

[1] https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-ci-centos-8-scenario010-standalone-network-master
[2] https://review.opendev.org/c/openstack/openstack-tempest-skiplist/+/801316
[3] https://sf.hosted.upshift.rdu2.redhat.com/zuul/t/tripleo-ci-internal/builds?job_name=periodic-tripleo-ci-rhel-8-scenario010-standalone-network-rhos-17
[4] https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-component-network/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-rhel-8-scenario010-standalone-network-rhos-17/70f8a6e/logs/undercloud/var/log/tempest/stestr_results.html