OpenStack DBaaS (Trove)

Notification exceptions not sent back correctly

Bug #1577848 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
High
Peter Stachowski
OpenStack DBaaS (Trove) newton-rc1 "RC1"
Mitaka
Fix Committed
High
Peter Stachowski
OpenStack DBaaS (Trove) next

Bug Description

With the new notification feature added recently, exceptions that occur on the guest are sent back to the conductor. Due to a mis-match in the code however, the wrong call is being issued. The conductor api is casting a call to notify_exception instead of notify_exc_info.

This needs to be changed.

Revision history for this message
Peter Stachowski (peterstac) wrote :

This is probably a candidate to push back to stable/mitaka

Changed in trove:
assignee: nobody → Peter Stachowski (peterstac)
milestone: none → newton-1
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/312166
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=9f7be1a10b0a53c6d8bd783a714fac2864186600
Submitter: Jenkins
Branch: master

commit 9f7be1a10b0a53c6d8bd783a714fac2864186600
Author: Peter Stachowski <email address hidden>
Date: Tue May 3 12:36:15 2016 -0400

    Notification exceptions not sent back correctly

    With the new notification feature added recently, exceptions
    that occur on the guest are sent back to the conductor.
    Due to a mis-match in the code however, the wrong call is being
    issued. The conductor api makes a call to notify_exception
    instead of notify_exc_info.

    This has been fixed.

    Change-Id: Ib2e04bb903c92b4d570913aba2e985db63c45096
    Closes-Bug: #1577848

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/314300

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (stable/mitaka)

Reviewed: https://review.openstack.org/314300
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=160c4f75caf23316e4b78f90adb2c603d9f7bbc8
Submitter: Jenkins
Branch: stable/mitaka

commit 160c4f75caf23316e4b78f90adb2c603d9f7bbc8
Author: Peter Stachowski <email address hidden>
Date: Tue May 3 12:36:15 2016 -0400

    Notification exceptions not sent back correctly

    With the new notification feature added recently, exceptions
    that occur on the guest are sent back to the conductor.
    Due to a mis-match in the code however, the wrong call is being
    issued. The conductor api makes a call to notify_exception
    instead of notify_exc_info.

    This has been fixed.

    Change-Id: Ib2e04bb903c92b4d570913aba2e985db63c45096
    Closes-Bug: #1577848
    (cherry picked from commit 9f7be1a10b0a53c6d8bd783a714fac2864186600)

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/trove 5.0.1

This issue was fixed in the openstack/trove 5.0.1 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/trove 6.0.0.0b2

This issue was fixed in the openstack/trove 6.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.