Actions
Bug #47373
closedmgr/dashboard: user can change the cluster of a NFS-Ganesha export
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Component - NFS
Target version:
% Done:
0%
Source:
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When editing an export, the user can change the cluster in the form.
This should be prohibited because the export belongs to a certain cluster.
Files
Updated by Kiefer Chang over 3 years ago
- Status changed from New to In Progress
- Assignee set to Kiefer Chang
Updated by Kiefer Chang over 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 37946
Updated by Lenz Grimmer over 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #48132: octopus: mgr/dashboard: user can change the cluster of a NFS-Ganesha export added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #48133: nautilus: mgr/dashboard: user can change the cluster of a NFS-Ganesha export added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 144 to Component - NFS
Actions