NetApp - Backing snapshots may not be deleted

[Chuck Fouts]

As part of the process of creating a consistency group snapshot a snapshot of the Cinder flexvol is taken. This snapshot may not be deleted if the snapshot is kept in a "busy" state that exceeds the existing retry logic. These snapshots need to be marked for later deletion so that they do not consume resources.

[OpenStack Infra (hudson-openstack)]

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

[Chuck Fouts (fchuck)]

Would really like to see this fix make Newton's RC1 cut. :)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/358789
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=388e52ce23b881f95f68f40458011433aee2808b
Submitter: Jenkins
Branch: master

commit 388e52ce23b881f95f68f40458011433aee2808b
Author: Chuck Fouts <email address hidden>
Date: Sun Jun 12 17:05:24 2016 -0400

    NetApp: Fix issue with busy snapshot deletion.

    This fixes the issue of deleting temporary snapshots created during the
    consistency group creation process. These temporary snapshots may not be
    deleted if the system is under load and the temporary snapshot remains
    in a "busy" state after the consistency group creation process is
    otherwise complete.

    This change also reduces lines of code by implementing a manager for the
    creation of FixedIntervalLoopingCall instances in the ONTAP drivers.
    This looping call manager also provides the ability to start all
    registered looping calls after the driver has been properly
    initialized. The looping call manager also makes it easy to ensure that
    FixedIntervalLoopingCall instances are not instantiated in Unit Tests.

    Closes-Bug: #1596679
    Change-Id: I13096a8c94a32e68814f81900032dbcc6a4a9806

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 9.0.0.0rc1 release candidate.