Tempest tests failed with Read timed out error on tripleo-ci-centos-7-undercloud-containers

Bug #1796710 reported by Martin Kopec
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

tripleo-ci-centos-7-undercloud-containers failed twice in gates with:

urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='192.168.24.3', port=8774): Read timed out. (read timeout=60)

In [3] failed [1] test and in the [4] failed [2] tests, however the [1] has passed. All of the tests [1][2] failed with the same Read timed out error, which may suggest a race condition.

[1] tempest.api.compute.admin.test_aggregates_negative.AggregatesAdminNegativeTestJSON.test_aggregate_add_non_exist_host

[2]
tempest.api.compute.admin.test_flavors_extra_specs.FlavorsExtraSpecsTestJSON
tempest.api.compute.admin.test_flavors_access_negative.FlavorsAccessNegativeTestJSON.test_flavor_non_admin_remove
tempest.api.compute.admin.test_flavors.FlavorsAdminTestJSON.test_create_list_flavor_without_extra_data

[3] http://logs.openstack.org/47/607147/7/gate/tripleo-ci-centos-7-undercloud-containers/0aef64e/logs/undercloud/home/zuul/tempest.log.txt.gz#_2018-10-08_15_21_04

[4] http://logs.openstack.org/51/586251/3/gate/tripleo-ci-centos-7-undercloud-containers/03a2fbd/logs/undercloud/home/zuul/tempest.log.txt.gz#_2018-10-07_22_05_03

Tags: ci
Martin Kopec (mkopec)
tags: added: alert
tags: added: promotion-blocker
wes hayutin (weshayutin)
Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
milestone: none → stein-1
Revision history for this message
chandan kumar (chkumar246) wrote :

From here I am not seeing these failures on ci jobs http://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-undercloud-containers. It might be a timed out issue while test run.

Revision history for this message
Marios Andreou (marios-b) wrote :

ack chandan, looking at tripleo-ci-centos-7-undercloud-containers the job is reporting green there and afaics all successful runs yesterday

Hm the skip is merging now (in the gate) https://review.openstack.org/#/c/608723 wondering if its better to let it merge and re-add or just stop it now?

tags: added: ci
removed: alert promotion-blocker
Revision history for this message
Marios Andreou (marios-b) wrote :

removed alert promotion-blocker adding ci tags

wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-quickstart-extras (master)

Change abandoned by Martin Kopec (<email address hidden>) on branch: master
Review: https://review.opendev.org/608723

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.