compute tempest tests failing in wallaby c8 featureset0035
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Compute tempest tests are failing with urllib3.
Failing tests:
setUpClass (tempest.
setUpClass (tempest.
setUpClass (tempest.
tempest.
tempest.
tempest.
I couldnt find any uuid to track from the tempest run log. So I checked compute log in general - nothing looks suspicious.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → yoga-3 |
tags: | added: ci promotion-blocker |
On Re-running https:/ /review. rdoproject. org/r/c/ testproject/ +/40101 fs035 here: /logserver. rdoproject. org/01/ 40101/2/ check/periodic- tripleo- ci-centos- 8-ovb-3ctlr_ 1comp-featurese t035-wallaby/ 8aea4cf/
https:/
``` ******* ******* ******* ******* ******* **** <body>< h1>504 Gateway Time-out</h1>\nThe server didn't respond in time.\n< /body>< /html>\ n"}, "msg": "Error updating router f2fc9134- 8e23-437e- bf3e-cb61204ad5 f2: Server Error for url: https://[2001:db8: fd00:1000: :5]:13696/ v2.0/routers/ f2fc9134- 8e23-437e- bf3e-cb61204ad5 f2, The server didn't respond in time.: 504 Gateway Time-out"}
TASK [os_tempest : Create router] *******
2022-03-09 07:20:37.738196 | primary | Wednesday 09 March 2022 07:20:37 +0000 (0:00:11.415) 1:41:23.679 *******
2022-03-09 07:22:44.839800 | primary | FAILED - RETRYING: Create router (5 retries left).
2022-03-09 07:24:57.456636 | primary | FAILED - RETRYING: Create router (4 retries left).
2022-03-09 07:27:23.480768 | primary | FAILED - RETRYING: Create router (3 retries left).
2022-03-09 07:28:28.385822 | primary | FAILED - RETRYING: Create router (2 retries left).
2022-03-09 07:30:40.801709 | primary | FAILED - RETRYING: Create router (1 retries left).
2022-03-09 07:32:53.502252 | primary | fatal: [undercloud -> undercloud]: FAILED! => {"attempts": 5, "changed": false, "extra_data": {"data": null, "details": "The server didn't respond in time.: 504 Gateway Time-out", "response": "<html>
```
Re-running again