Comment 2 for bug 1348204

Revision history for this message
Matt Riedemann (mriedem) wrote :

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRmlsZSBcXFwidGVtcGVzdC9zY2VuYXJpby90ZXN0X2VuY3J5cHRlZF9jaW5kZXJfdm9sdW1lcy5weVxcXCJcIiBBTkQgbWVzc2FnZTpcImluIHRlc3RfZW5jcnlwdGVkX2NpbmRlcl92b2x1bWVzX2NyeXB0c2V0dXBcIiBBTkQgdGFnczpcImNvbnNvbGVcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNjIxNDQ1NzQ2NH0=

132 hits in 7 days, all failures, multiple queues.

The fingerprint isn't great but we don't have a trace in tempest.txt log and we don't have any good errors in the cinder logs that appear to be related to this, so it just seems like a routine timeout that we'll have to manage somehow.