Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1858826

Summary: mgr/volumes: Remove 'protect' and 'unprotect' requirements to clone a subvolume snapshot
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Shyamsundar <srangana>
Component: CephFSAssignee: Shyamsundar <srangana>
Status: CLOSED UPSTREAM QA Contact: subhash <vpoliset>
Severity: high Docs Contact:
Priority: high    
Version: 5.0CC: ceph-eng-bugs, pdonnell, sweil, vpoliset
Target Milestone: ---   
Target Release: 5.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1857827 Environment:
Last Closed: 2020-07-31 21:58:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shyamsundar 2020-07-20 13:50:28 UTC 
+++ This bug was initially created as a clone of Bug #1857827 +++

Subvolume snapshots required to be protected, prior to cloning the same.

Also, protected snapshots were not allowed to be unprotected or removed, if there were in-flight clones, whose source was the snapshot being removed.

The protection of snapshots explicitly is not required, as these can be prevented from being removed based only on the in-flight clones checks.

These calls should hence be deprecated, and this allows a clone to be a simpler implementation for consumers like ceph-csi.

In addition to deprecating the above, add support to query a subvolume for supported features, via the subvolume info command, to assist with a Ceph version based  decision on when to use these calls prior to cloning the subvolume.