Actions
Bug #46369
openmgr/dashboard: RBD namspace creation form gives incorrect hint when creating namespaces
Status:
Fix Under Review
Priority:
Low
Assignee:
Category:
Component - RBD
Target version:
-
% Done:
100%
Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The RBD namespace creation form displays `Namespace already exists` even it's doesn't.
Not 100% sure, but it seems only to happen in Octopus + Firefox.
Files
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 139 to Component - RBD
Updated by Kumar Navin Barnwal about 3 years ago
- File Screenshot from 2021-04-23 14-44-55.png Screenshot from 2021-04-23 14-44-55.png added
- Status changed from New to In Progress
- Pull request ID set to 40999
Updated by Kumar Navin Barnwal about 3 years ago
- File Screenshot from 2021-04-23 14-44-55.png Screenshot from 2021-04-23 14-44-55.png added
- Pull request ID changed from 40999 to 40664
Fixed !
Updated by Kumar Navin Barnwal about 3 years ago
- Status changed from In Progress to Fix Under Review
Updated by Kumar Navin Barnwal about 3 years ago
- Pull request ID changed from 40664 to 41001
Updated by Kumar Navin Barnwal about 3 years ago
- Subject changed from mgr/dashboard: RBD namspace creation form gives incorrect hint when creating namespaces to [Dashboard - Bug #46369] (Resolved) mgr/dashboard: RBD namspace creation form gives incorrect hint when creating namespaces
- Pull request ID changed from 41001 to 41008
Updated by Kumar Navin Barnwal almost 3 years ago
- Subject changed from [Dashboard - Bug #46369] (Resolved) mgr/dashboard: RBD namspace creation form gives incorrect hint when creating namespaces to mgr/dashboard: RBD namspace creation form gives incorrect hint when creating namespaces
- Status changed from Fix Under Review to Resolved
- % Done changed from 0 to 100
- Pull request ID changed from 41008 to 41058
Updated by Nizamudeen A almost 3 years ago
- Status changed from Resolved to Fix Under Review
Navin: The issue is Resolved only when the PR you raised is merged. For now I am keeping it in Fix Under Review. Once PR is merged it can be moved to Resolved
Actions