Bug 2231342 - Ceph dashboard allows to set invalid value for quota value for max bytes which leads to wrongful setting of quota
Summary: Ceph dashboard allows to set invalid value for quota value for max bytes whic...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Dashboard
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 7.1
Assignee: Nizamudeen
QA Contact: Sayalee
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-11 09:54 UTC by ngangadh
Modified: 2023-08-11 09:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7193 0 None None None 2023-08-11 09:55:19 UTC
Red Hat Issue Tracker RHCSDASH-1052 0 None None None 2023-08-11 09:55:23 UTC

Description ngangadh 2023-08-11 09:54:31 UTC 
Description of problem: Ceph dashboard allows to set invalid value for quota value for max bytes which leads to wrongful setting of quota  


Version-Release number of selected component (if applicable): 7.0 


How reproducible: 5/5


Steps to Reproduce:
1. Create a cephfs mount either userspace or kernel. 
2. Create a directory inside the mount.
3. From UI dashboard, try setting the max_bytes quota.
4. If for any reason, user enters a symbol between the numbers like typo. Eg: User wants to set 10000, however ends up typing 100_00 then the notification says quota set successfully. 
5. Verify from UI and CLI, the set quota would be only 100 and not 10000 which would be wrongful setting of quota and notification. 

Actual results: Quota is allowed to set with invalid characters 


Expected results: Quota value should be validated in UI when entered by user and should not allow such values to be set. 
A proper error message saying 'Please enter a valid quota' needs to be displayed. 


Additional info:
Note You need to log in before you can comment on or make changes to this bug.