InstanceNotFound exceptions should not log stack traces in compute logs
Bug #933012 reported by
Alex Meade
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Nikhil Komawar | ||
Bug Description
Everytime an InstanceNotFound exception is raised in compute manager, it logs an ERROR containing a stack trace from the amqp call. We should just log a warning that an instance could not be found.
| Changed in nova: | |
| assignee: | nobody → Alex Meade (alex-meade) |
| status: | New → In Progress |
| Changed in nova: | |
| assignee: | Alex Meade (alex-meade) → nikhil komawar (nikhil-komawar) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → essex-4 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit fcbba45dcf09f60
Author: Nikhil Komawar <email address hidden>
Date: Fri Feb 17 02:24:08 2012 +0000
InstanceNot
instead of throwing exeptions.
fixes bug 933012
Change-Id: Ib6c6c33e26125b