Bug 2303196
Summary: | [NFS] [Dashboard] Export creation directly on cephFS fileysystem is working. It should not allow to create the export directly on cephFS filesystem via dashboard | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manisha Saini <msaini> |
Component: | Ceph-Dashboard | Assignee: | dtalweka |
Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
Severity: | high | Docs Contact: | Akash Raj <akraj> |
Priority: | unspecified | ||
Version: | 8.0 | CC: | akraj, ceph-eng-bugs, cephqe-warriors, dtalweka, nia, rpollack, tserlin |
Target Milestone: | --- | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-19.2.0-4.el9cp | Doc Type: | Bug Fix |
Doc Text: |
.Users are now prompted to enter a path when creating an export
Previously, creating an export was not prompting for a path and by default `/` was entered.
With this fix, when attempting to create the export directly on the file system, it prompts for a path. If an invalid path is entered, creation is not permitted. Additionally, when entering the path of the CephFS file system directly, a warning appears stating "Export on CephFS volume '/' not allowed".
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-11-25 09:04:24 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: | 2298636, 2317218 |
Description
Manisha Saini
2024-08-06 16:01:55 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 (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 |