Registry client request GET /images/UUID raised ClientConnectionError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
From tempest:
2013-10-14 20:57:53.231 | FAIL: setUpClass (tempest.
2013-10-14 20:57:53.231 | setUpClass (tempest.
2013-10-14 20:57:53.231 | -------
2013-10-14 20:57:53.232 | _StringException: Traceback (most recent call last):
2013-10-14 20:57:53.232 | File "tempest/
2013-10-14 20:57:53.232 | cls.client.
2013-10-14 20:57:53.233 | File "tempest/
2013-10-14 20:57:53.233 | raise exceptions.
2013-10-14 20:57:53.233 | TimeoutException: Request timed out
I'm not sure they're related, but there's about a 5 second gap in both the tempest and glance logs around the time of this failure (near 2013-10-14 20:44:30.948), and a Not Found reported at about the same time in the glance logs:
screen-g-reg.txt.gz contains:
2013-10-14 20:44:28.170 20481 DEBUG glance.
2013-10-14 20:44:28.171 20481 INFO glance.
screen-g-api.txt.gz contains:
2013-10-14 20:44:28.173 20525 INFO glance.
2013-10-14 20:44:28.173 20525 DEBUG glance.
summary: |
- "TimeoutException: Request timed out" on - tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestXML + Registry client request GET /images/UUID raised ClientConnectionError |
Changed in glance: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | icehouse-2 → 2014.1 |
not found get_image_ meta_or_ 404 is found in many successful runs so not clear if that is related. FOr now here is a logstash query that checks tempest output:
@message: "tempest/ services" AND @message: "/images_ client. py" AND @message: "wait_for_ image_status" AND @tags:" console. html"