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.
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 4.1 Bug Fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4144