Bug 2269104
Summary: | [Dashboard][Cephfs]Cloning subvolume not listing _nogroup subvolumegroup if there are no subvols in _nogroup | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Amarnath <amk> |
Component: | Ceph-Dashboard | Assignee: | dtalweka |
Status: | CLOSED ERRATA | QA Contact: | Amarnath <amk> |
Severity: | high | Docs Contact: | Akash Raj <akraj> |
Priority: | high | ||
Version: | 7.1 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, dtalweka, mobisht, nia, rpollack, tserlin |
Target Milestone: | --- | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-19.1.1-80.el9cp | Doc Type: | Bug Fix |
Doc Text: |
.`_nogroup` is now listed in the *Subvolume Group* list even if there are no subvolumes in `_nogroup`
Previously, while cloning subvolume, `_nogroup` subvolume group was not listed if there were no subvolumes in `_nogroup`. As a result, users were not able to select `_nogroup` as a subvolume group.
With this fix, while cloning a subvolume, `_nogroup` is listed in the *Subvolume Group* list, even if there are no subvolumes in `_nogroup`.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-11-25 09:00:50 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: | |||
Bug Depends On: | |||
Bug Blocks: | 2317218 |
Description
Amarnath
2024-03-12 04:48:22 UTC
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 8.0 security, bug fix, and enhancement updates), 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-2024:10216 |