OpenStack Compute (nova)

Migration 112 breaks if deleted_at is NULL

Bug #1029129 reported by Rick Harris
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Rick Harris
OpenStack Compute (nova) 2012.2 "folsom"
Rick Harris (rconradharris)
Changed in nova:
assignee: nobody → Rick Harris (rconradharris)
importance: Undecided → High
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/10297
Committed: http://github.com/openstack/nova/commit/a8c08baeb2ee6268ac61613a23cc86cf885a9d09
Submitter: Jenkins
Branch: master

commit a8c08baeb2ee6268ac61613a23cc86cf885a9d09
Author: Rick Harris <email address hidden>
Date: Wed Jul 25 20:43:17 2012 +0000

    Handle NULL deleted_at in migration 112.

    A NULL value in `instance.deleted_at` will cause the migration to break.
    In the absence of instance deleted_at timestamp, we should be
    conservative and skip cleanup.

    Fixes bug 1029129

    Change-Id: Ieb978281bc55727fb7db02ddc8c3e0fd6c8814f0

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → folsom-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: folsom-3 → 2012.2
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.