update_statuses_on_time_out looks up an instance from the DB by name

Bug #1356647 reported by Nikhil Manchanda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Critical
Nikhil Manchanda

Bug Description

update_statuses_on_time_out moves an instance from BUILD state to ERROR state in case it has been building for longer than a "usage_timeout" value (s).

However, it looks up the instance by name instead of ID. This potentially means that we update the wrong instance to ERROR, since name is not unique.

https://github.com/openstack/trove/blob/master/trove/taskmanager/models.py#L291-294

Changed in trove:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Nikhil Manchanda (slicknik)
milestone: none → juno-3
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/114095

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

Reviewed: https://review.openstack.org/114095
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=52e1dc1b754fea6ec554c53e59df72606a8a36c4
Submitter: Jenkins
Branch: master

commit 52e1dc1b754fea6ec554c53e59df72606a8a36c4
Author: Nikhil Manchanda <email address hidden>
Date: Wed Aug 13 18:00:34 2014 -0700

    Look up trove instance by ID instead of name

    update_statuses_on_time_out looks up the instance by name instead of ID.
    This potentially means that we update the wrong instance to ERROR, since
    instance name is not unique. This patchset fixes this issue by looking
    up the trove instance by ID instead of name.

    Change-Id: If9c7a518f50098390567d8e4df0f948b7d3be2c6
    Closes-bug: 1356647

Changed in trove:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in trove:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in trove:
milestone: juno-3 → 2014.2
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.