Bug 2359188
| Summary: | QoS values configured via CLI in gigabytes are displayed in bytes on the Dashboard, which reduces clarity and makes the information less user-friendly | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Manisha Saini <msaini> |
| Component: | Ceph-Dashboard | Assignee: | naman munet <nmunet> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | medium | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 8.1 | CC: | afrahman, anbehl, ceph-eng-bugs, cephqe-warriors, dtalweka, hyelloji, nia, nmunet, tserlin |
| Target Milestone: | --- | ||
| Target Release: | 8.1z3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-19.2.1-249.el9cp | Doc Type: | No Doc Update |
| Doc Text: |
No doc text needed
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-09-30 09:21:58 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: | |||
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.1 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-2025:17047 |
Description of problem: ========= Set the cluster-level QoS limits via the CLI (in GB) and verify the values on the Dashboard. Initially, the values are displayed in bytes, which are harder to interpret. However, when you click on specific Dashboard fields (e.g., export read bandwidth), the values update to GB, matching what was configured via the CLI. # ceph nfs cluster qos enable bandwidth_control nfsganesha PerShare --max_export_write_bw 2GB --max_export_read_bw 3GB [ceph: root@ceph-nfsclusterlive-vbrwai-node1-installer /]# ceph nfs cluster qos get nfsganesha { "combined_rw_bw_control": false, "enable_bw_control": true, "enable_iops_control": false, "enable_qos": true, "max_export_read_bw": "3.0GB", "max_export_write_bw": "2.0GB", "qos_type": "PerShare" } Dashboard ---- Bandwidth QOS Type Per Share Allows individual per share setting of export and client bandwidth Export read bandwidth (required) 3000000000 Limits the maximum bandwidth that can be used for export read per second Export write bandwidth (required) 2000000000 Limits the maximum bandwidth that can be used for export write per second ------ Click on the fields on Dashboard --> The values are now shown in GB ------ Bandwidth QOS Type Per Share Allows individual per share setting of export and client bandwidth Export read bandwidth (required) 2.8 GiB/s Limits the maximum bandwidth that can be used for export read per second Export write bandwidth (required) 1.9 GiB/s Limits the maximum bandwidth that can be used for export write per second Version-Release number of selected component (if applicable): ---------- # ceph --version ceph version 19.2.1-126.el9cp (cfd2907537ba633f7d638895efd70ef5d0f1c99b) squid (stable) How reproducible: ----- 2/2 Steps to Reproduce: ------- 1. Set the QoS values at cluster level from Dashboard CLI # ceph nfs cluster qos enable bandwidth_control nfsganesha PerShare --max_export_write_bw 2GB --max_export_read_bw 3GB # ceph nfs cluster qos get nfsganesha { "combined_rw_bw_control": false, "enable_bw_control": true, "enable_iops_control": false, "enable_qos": true, "max_export_read_bw": "3.0GB", "max_export_write_bw": "2.0GB", "qos_type": "PerShare" } 2. Check the Values set at cluster level from Dashboard Actual Results: -------- The values appear in Bytes on the Dashboard, even though they were set in GB via the CLI. Upon clicking the respective fields on the Dashboard, the units update and display in GB. Expected Results: -------- When QoS limits are set in GB via CLI, the Dashboard should consistently display them in GB for better readability and user clarity. Additional info: