No fault attr on server can cause error

Bug #1642636 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
High
Peter Stachowski

Bug Description

If an error occurs on the server, but there is no server.fault attribute the trove code will throw an exception. This case needs to be handled.

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/399104

Changed in trove:
assignee: nobody → Peter Stachowski (peterstac)
status: New → In Progress
Changed in trove:
importance: Undecided → High
milestone: none → next
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/399104
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=4895f6b68e15ed50685d747a4f2687e0359e0527
Submitter: Jenkins
Branch: master

commit 4895f6b68e15ed50685d747a4f2687e0359e0527
Author: Peter Stachowski <email address hidden>
Date: Thu Nov 17 10:52:48 2016 -0500

    Fix error case where server.fault is missing

    Some times when there's a server error, there is no
    'fault' attribute on the server record. This caused
    Trove to throw an exception. This has been fixed.

    Change-Id: I47cbe9e899cb0767c377d184f123e38eda5b6a05
    Depends-On: Ia4fc545a10c7c16532aefd73818dd7d90c9c271b
    Closes-Bug: #1642636

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/trove 7.0.0.0b2

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

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

Other bug subscribers

Remote bug watches

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