Bug 2240138 - [cephfs][dashboard] subvolume group delete did not allow.
Summary: [cephfs][dashboard] subvolume group delete did not allow.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 7.1
Assignee: Neeraj Pratap Singh
QA Contact: julpark
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks: 2240729 2240727 2267614 2298578 2298579
TreeView+ depends on / blocked
 
Reported: 2023-09-21 23:39 UTC by julpark
Modified: 2024-07-18 07:59 UTC (History)
8 users (show)

Fixed In Version: ceph-18.2.1-20.el9cp
Doc Type: Bug Fix
Doc Text:
.The `ENOTEMPTY` output is detected and the message is displayed correctly Previously, when running the `subvolume group rm` command, the `ENOTEMPTY` output was not detected in the volume's plugin causing a generalized error message instead of a specific message. With this fix, the `ENOTEMPTY` output is detected for the `subvolume group rm` command when there is subvolume present inside the subvolumegroup and the message is displayed correctly.
Clone Of:
: 2240727 2240729 (view as bug list)
Environment:
Last Closed: 2024-06-13 14:21:37 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 62968 0 None None None 2023-09-25 11:54:36 UTC
Red Hat Issue Tracker RHCEPH-7517 0 None None None 2023-09-21 23:43:45 UTC
Red Hat Product Errata RHSA-2024:3925 0 None None None 2024-06-13 14:21:51 UTC

Comment 18 errata-xmlrpc 2024-06-13 14:21:37 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 (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and 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/RHSA-2024:3925
Note You need to log in before you can comment on or make changes to this bug.