quantum manager eats exceptions during deallocation

Bug #931801 reported by Aaron Lee on 2012-02-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Aaron Lee

Bug Description

deallocate_ip_address and deallocate_port log a message, but don't log the exception. Johannes brought this up during a review and suggested we run down why these exceptions are not logged.

Fix proposed to branch: master
Review: https://review.openstack.org/4729

Changed in nova:
assignee: nobody → Aaron Lee (aaron-lee)
status: New → In Progress

Reviewed: https://review.openstack.org/4729
Committed: http://github.com/openstack/nova/commit/29d021ba9063a9db16b29a327af9581b58a8e2f7
Submitter: Jenkins
Branch: master

commit 29d021ba9063a9db16b29a327af9581b58a8e2f7
Author: Aaron Lee <email address hidden>
Date: Wed Feb 29 17:07:39 2012 -0600

    Fixes lp931801 and a key_error

    The quantum manager should log the errors it
    receives from quantum, even when charging ahead
    with the deletes.

    update: pep8 and less some testing code
    update: checking log is called and consolidate
            error messages

    Change-Id: I8f533e8e54c5e4487614a61a73d9c8e2e756058d

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

Other bug subscribers