periodic-tripleo-ci-centos-9-8-multinode-mixed-os consistent failing in NetworkBasicOps tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This seems to be related to network:
Traceback (most recent call last):
File "/usr/lib/
return f(*func_args, **func_kwargs)
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib64/
raise self.failureExc
AssertionError: False is not true : Public network connectivity check failed
Timed out waiting for 192.168.24.190 to become reachable
All tempest.
Example logs:
Changed in tripleo: | |
importance: | Undecided → Critical |
Arx can we try this on vexx to see if it is env specific please?
Currently this is ibmcloud via the nodeset @ https:/ /github. com/rdo- infra/rdo- jobs/blob/ f9e7e03915ec3f8 5700ae8f60e3eb0 d37dc733af/ zuul.d/ integration- pipeline- wallaby- centos9. yaml#LL69C22- L69C53
&
https:/ /github. com/rdo- infra/rdo- jobs/blob/ f9e7e03915ec3f8 5700ae8f60e3eb0 d37dc733af/ zuul.d/ nodesets. yaml#L659 9-one-centos- 8-nodes- ibm-bm3
name: two-centos-
vs
https:/ /github. com/rdo- infra/rdo- jobs/blob/ f9e7e03915ec3f8 5700ae8f60e3eb0 d37dc733af/ zuul.d/ nodesets. yaml#L529 9-one-centos- 8-nodes
name: two-centos-