fs001 network wallaby fails with Server failed to reach ACTIVE status and task state "None" within the required time issue

[Soniya Murlidhar Vyas]

Periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001-network-wallaby fails on tempest tests

tempest.scenario.test_network_basic_ops.TestNetworkBasicOps tests.

Following is the traceback for tempest tests failure observed:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/tempest/common/utils/__init__.py", line 70, in wrapper
    return f(*func_args, **func_kwargs)
  File "/usr/lib/python3.6/site-packages/tempest/scenario/test_network_basic_ops.py", line 443, in test_network_basic_ops
    self._reassociate_floating_ips()
  File "/usr/lib/python3.6/site-packages/tempest/scenario/test_network_basic_ops.py", line 226, in _reassociate_floating_ips
    server = self._create_server(self.network)
  File "/usr/lib/python3.6/site-packages/tempest/scenario/test_network_basic_ops.py", line 172, in _create_server
    security_groups=security_groups)
  File "/usr/li/python3.6/site-packages/tempest/scenario/manager.py", line 314, in create_server
    image_id=image_id, **kwargs)
  File "/usr/lib/python3.6/site-packages/tempest/common/compute.py", line 268, in create_test_server
    server['id'])
  File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__
    self.force_reraise()
  File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise
    raise self.value
  File "/usr/lib/python3.6/site-packages/tempest/common/compute.py", line 239, in create_test_server
    request_id=request_id)
  File "/usr/lib/python3.6/site-packages/tempest/common/waiters.py", line 100, in wait_for_server_status
    raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (TestNetworkBasicOps:test_network_basic_ops) Server 838056c9-88df-4c79-9d41-c0a104da9e5a failed to reach ACTIVE status and task state "None" within the required time

For more details please refer the following links:-

1. https://logserver.rdoproject.org/openstack-component-network/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001-network-wallaby/ab9dd70/logs/undercloud/var/log/tempest/stestr_results.html.gz
2. https://logserver.rdoproject.org/60/39960/17/check/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset001-network-wallaby/21ed985/logs/undercloud/var/log/tempest/stestr_results.html.gz

[Soniya Murlidhar Vyas (svyas)]

Same issue is seen with - periodic-tripleo-ci-centos-9-standalone-compute-master and periodic-tripleo-ci-centos-9-standalone-full-tempest-api-compute-master

[Soniya Murlidhar Vyas (svyas)]

latest run of centos-9-standalone-network-master, centos-9-containers-multinode-network-master is also hitting similar issue.

- https://logserver.rdoproject.org/openstack-component-network/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-standalone-network-master/9ec970b/logs/undercloud/var/log/tempest/stestr_results.html.gz
- https://logserver.rdoproject.org/openstack-component-network/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-containers-multinode-network-master/9f56620/logs/undercloud/var/log/tempest/stestr_results.html.gz

[Marios Andreou (marios-b)]

marked as duplicate for https://bugs.launchpad.net/tripleo/+bug/1964940