InstanceNotFound exceptions should not log stack traces in compute logs

Bug #933012 reported by Alex Meade on 2012-02-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
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.

Alex Meade (alex-meade) on 2012-02-15
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)

Submitter: Jenkins
Branch: master

commit fcbba45dcf09f6087fabfaff1bcb960f0693ae76
Author: Nikhil Komawar <email address hidden>
Date: Fri Feb 17 02:24:08 2012 +0000

    InstanceNotFound exceptions for terminate_intance now Log warning
    instead of throwing exeptions.

    fixes bug 933012

    Change-Id: Ib6c6c33e26125b561bd5a1bc1e710016746e7e44

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-02-29
Changed in nova:
milestone: none → essex-4
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers