Nexenta volume driver leaves snapshot uremoved

Bug #1246079 reported by Mikhail Khodos on 2013-10-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Undecided
Mikhail Khodos

Bug Description

After deletion of a volume which was created by cloning Nexenta backend still contains snapshot used for cloning.

Changed in cinder:
assignee: nobody → Mikhail Khodos (hodosmb)
status: New → In Progress

Reviewed: https://review.openstack.org/54166
Committed: http://github.com/openstack/cinder/commit/e7319bcebdc225a4b7f784acebbf2cd00f3a3e3b
Submitter: Jenkins
Branch: master

commit e7319bcebdc225a4b7f784acebbf2cd00f3a3e3b
Author: keystone <email address hidden>
Date: Mon Oct 28 12:29:24 2013 -0700

    Nexenta: Remove snapshot after volume-clone deletion.

    Detect if volume was created via cloning and remove a snapshot from the
    appliance if so. Return 'provider_location' to update the volume DB record
    after creating a volume via cloning.

    Closes-Bug: #1246079
    Change-Id: I6c946d34871119600d7197614f5be22fa926e5dc

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-12-04
Changed in cinder:
milestone: none → icehouse-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2014-04-17
Changed in cinder:
milestone: icehouse-1 → 2014.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers