Ack Matthew, i still don't see it.
** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1351333
Title:
Don't trace for image not found from glanceclient
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Take this for example:
http://logs.openstack.org/31/111131/2/gate/gate-tempest-dsvm-
full/58b9b4d/logs/screen-n-cpu.txt.gz?level=TRACE
In a normal tempest run we generate a lot of errors for "Request
returned failure status 404." from glanceclient, in negative tests so
this is expected and normal in a tempest run.
On this query:
message:"Request returned failure status 404" AND
module:"glanceclient.common.http" AND tags:"screen-n-cpu.txt"
In a week we get nearly 60K hits on that:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiUmVxdWVzdCByZXR1cm5lZCBmYWlsdXJlIHN0YXR1cyA0MDRcIiBBTkQgbW9kdWxlOlwiZ2xhbmNlY2xpZW50LmNvbW1vbi5odHRwXCIgQU5EIHRhZ3M6XCJzY3JlZW4tbi1jcHUudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MDY5MDI4Mjg0NjF9
In a non-tempest scenario, would this really necessitate an
error/trace, i.e. does an operator need to be called up in the middle
of the night to fix an 'image not found' situation? The user might
have goofed and tried booting an instance with image 'foo'.
So we should just drop this to something less than error, maybe
warning to start.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1351333/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
