NetApp delete snapshot with ongoing clone split

Bug #2025641 reported by Maurice Escher
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
In Progress
Medium
kiran pawar

Bug Description

Hi,

please have a look at:
https://paste.opendev.org/show/820541/

I have Manila Xena with ONTAP 9.10 back end and set netapp:split_clone_on_create to "True".
What happened: a share was created from a snapshot, clone split was ongoing. A snapshot of this share had been created and delete of this snapshot went into above error. All happened within 15 minutes (part of a CI/CD) after share create, clone split was still ongoing.

So the fallback to deferred deletion would not work, because even a simple rename of the snapshot is blocked on the NetApp backend during clone split (busy volume).

Maybe the split job needs to be paused and resumed during this rename? Or the deferred deletion needs another marker, maybe the comment field can be modified or a tag being set?

BR,
Maurice

And please see the related issue https://bugs.launchpad.net/manila/+bug/1960239.

Vida Haririan (vhariria)
tags: added: netapp
Vida Haririan (vhariria)
tags: added: snapshot
Vida Haririan (vhariria)
Changed in manila:
assignee: nobody → Felipe Rodrigues (felipefutty)
status: New → Triaged
milestone: none → bobcat-3
importance: Undecided → Medium
Revision history for this message
Vida Haririan (vhariria) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/manila/+/894637

Changed in manila:
status: Triaged → In Progress
Changed in manila:
assignee: Felipe Rodrigues (felipefutty) → kiran pawar (kpdev)
Changed in manila:
milestone: bobcat-3 → caracal-1
Changed in manila:
milestone: caracal-1 → caracal-2
Changed in manila:
milestone: caracal-2 → caracal-3
Changed in manila:
milestone: caracal-3 → dalmation-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.