tripleo

compute tempest tests failing in wallaby c8 featureset0035

Bug #1964199 reported by Ananya Banerjee on 2022-03-08

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tripleo	Fix Released	Critical	Unassigned	tripleo yoga-3

Bug Description

Compute tempest tests are failing with urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='2001:db8:fd00:1000::5', port=13696): Read timed out. (read timeout=60)

tempest run log: https://logserver.rdoproject.org/62/40162/6/check/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby/7911fdc/logs/undercloud/var/log/tempest/tempest_run.log.txt.gz

Failing tests:
setUpClass (tempest.api.compute.floating_ips.test_list_floating_ips.FloatingIPDetailsTestJSON)
setUpClass (tempest.api.compute.security_groups.test_security_groups_negative.SecurityGroupsNegativeTestJSON)
setUpClass (tempest.api.compute.servers.test_create_server.ServersTestJSON)
tempest.api.compute.servers.test_attach_interfaces.AttachInterfacesTestJSON.test_create_list_show_delete_interfaces_by_network_port[id-73fe8f02-590d-4bf1-b184-e9ca81065051,network]
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard[id-2cb1baf6-ac8d-4429-bf0d-ba8a0ba53e32,smoke]
tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_rebuild_server[id-aaa6cdf3-55a7-461a-add9-1c8596b9a07c]

I couldnt find any uuid to track from the tempest run log. So I checked compute log in general - nothing looks suspicious.

Tags:

Ananya Banerjee (frenzyfriday) on 2022-03-08

Changed in tripleo:
status:	New → Triaged
importance:	Undecided → Critical
milestone:	none → yoga-3
tags:	added: ci promotion-blocker

Revision history for this message

chandan kumar (chkumar246) wrote on 2022-03-09:

On Re-running https://review.rdoproject.org/r/c/testproject/+/40101 fs035 here:
https://logserver.rdoproject.org/01/40101/2/check/periodic-tripleo-ci-centos-8-ovb-3ctlr_1comp-featureset035-wallaby/8aea4cf/

```
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><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-cb61204ad5f2: Server Error for url: https://[2001:db8:fd00:1000::5]:13696/v2.0/routers/f2fc9134-8e23-437e-bf3e-cb61204ad5f2, The server didn't respond in time.: 504 Gateway Time-out"}
```