NetApp cDOT tries to release and destroy snap mirrors to the same volume

[Goutham Pacha Ravi]

NetApp cDOT Snapmirrors cannot be established from one FlexVol to itself, however, the cDOT driver in Manila issues ZAPIs to delete/release snap mirrors between the volume and itself. This needs to be cleaned up.

 Request: <netapp xmlns="http://www.netapp.com/filer/admin" version="1.21" vfiler="vserver_38fdbbc6">
 <snapmirror-destroy-iter>
 <query>
 <snapmirror-info>
  <source-vserver>vserver_38fdbbc6</source-vserver>
  <source-volume>share_b60df35f_73b3_43ca_8ead_ae8b96e61517</source-volume>
   <destination-vserver>vserver_38fdbbc6</destination-vserver>
  <destination-volume>share_b60df35f_73b3_43ca_8ead_ae8b96e61517</destination-volume>
 </snapmirror-info>
 </query>
 </snapmirror-destroy-iter>
</netapp>

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/366935
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=8cc148fe91c0af3c457ff5fdc0d3d1e9b97949fa
Submitter: Jenkins
Branch: master

commit 8cc148fe91c0af3c457ff5fdc0d3d1e9b97949fa
Author: Goutham Pacha Ravi <email address hidden>
Date: Tue Sep 6 20:13:35 2016 -0400

    NetApp cDOT: Avoid cleaning up 'invalid' mirrors

    NetApp cDOT SnapMirrors cannot be established from one
    FlexVol to itself, however, the cDOT driver issues ZAPIs to
    delete/release SnapMirrors between the volume and itself.

    Avoid this behavior and add unit test coverage.

    Change-Id: I8ca096dfe8463511595a67cbea3ca31a80c0e5fb
    Closes-Bug: #1578328

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 3.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila 3.0.0 release.