Extra specs of instance type (flavor) remain after instance type deletion/purge

Bug #854930 reported by Vladimir Popovski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Vish Ishaya

Bug Description

instance_type_destroy() & instance_type_purge() functions of nova.db.sqlalchemy.api delete/purge only records in InstanceTypes and don't delete associated extra specs.

Same issue is relevant for volume types - volume_type_destroy() & volume_type_purge()

Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Medium
status: New → Confirmed
Maru Newby (maru)
Changed in nova:
assignee: nobody → Maru Newby (maru)
Maru Newby (maru)
Changed in nova:
assignee: Maru Newby (maru) → nobody
Changed in nova:
assignee: nobody → Vish Ishaya (vishvananda)
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/3739

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

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

commit faa938c1650d892b945795112eb2850212b28ccb
Author: Vishvananda Ishaya <email address hidden>
Date: Thu Feb 2 18:53:17 2012 -0800

    Removes constraints from instance and volume types

     * Gets rid of annoying purge semantics
     * removes unique constraints from the db
     * deletes extra specs when a volume is deleted
     * adds exceptions for when the type already exists
     * fixes bug 854930
     * fixes bug 925823

    Change-Id: I4618759e31501b2e85325f4e9b9895f04dc151d0

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