Migrations fail when dropping a non-existent index

Bug #1243553 reported by Mahesh Panchaksharaiah
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Mahesh Panchaksharaiah

Bug Description

Migrations which modify indexes first drop the existing index before creating a new one. If the index is missing for some reason the migration fails.

Changed in nova:
assignee: nobody → Mahesh Panchaksharaiah (maheshp)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

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

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

commit aadc7b89131f3d46070e7e5478156e3cf623dbe6
Author: Mahesh Panchaksharaiah <email address hidden>
Date: Wed Oct 23 15:42:59 2013 +0530

    Checking existence of index before dropping

    Migrations modifying indexes drop and recreate the index.
    If an index does not exist dropping would fail the migration.
    As part of this fix, checking if index exists before dropping it.

    Fixes bug 1243553

    Change-Id: Ic75744bdccfbc516d36a9711ad6997fd86c7a722

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