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

Bug #1796710 reported by Martin Kopec on 2018-10-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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

urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='', 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


[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 Edit Tag help
Martin Kopec (mkopec) on 2018-10-08
tags: added: alert
tags: added: promotion-blocker
wes hayutin (weshayutin) on 2018-10-08
Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
milestone: none → stein-1
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.

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
Marios Andreou (marios-b) wrote :

removed alert promotion-blocker adding ci tags

wes hayutin (weshayutin) on 2018-10-11
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers