Bug 2125575

Summary: [CephFS] mgr/volumes: display in-progress clones for a snapshot
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Kotresh HR <khiremat>
Component: CephFSAssignee: Kotresh HR <khiremat>
Status: CLOSED ERRATA QA Contact: Amarnath <amk>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: ceph-eng-bugs, cephqe-warriors, hyelloji, mmuench, tserlin, vshankar
Target Milestone: ---   
Target Release: 5.3z1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-16.2.10-100.el8cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-28 10:05:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kotresh HR 2022-09-09 10:37:31 UTC
Description of problem:
Right now, there is no way of knowing the set of clone operations n-progress/pending for a subvolume snapshot (unless one knows the clone subvolume name and use `clone status` to infer the details).

Introduce a way to list in-progress/pending clones for a subvolume snapshot. This would involve fetching "clone indexes" from subvolume metadata and resolving the index to the target subvolume (clone).

Please check the upstream tracker attached for more information.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 RHEL Program Management 2022-09-09 10:37:39 UTC
Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 12 errata-xmlrpc 2023-02-28 10:05:18 UTC
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 (Important: Red Hat Ceph Storage 5.3 Bug fix and security 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/RHSA-2023:0980