Actions
Bug #39714
closedmgr/dashboard: Pool read/write OPS shows too many decimal places
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Component - Pools
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Files
Updated by Lenz Grimmer about 4 years ago
- Translation missing: en.field_tag_list set to low-hanging-fruit, usability
- Subject changed from mgr/dashboard: Pool read/write OPS shows to many decimal places to mgr/dashboard: Pool read/write OPS shows too many decimal places
- Tags deleted (
low-hanging-fruit)
Updated by Stephan Müller about 4 years ago
- Has duplicate Bug #41345: mgr/dashboard: Read ops values should be rounded added
Updated by anurag bandhu about 4 years ago
I think Write-ops also need to be rounded off
Updated by Stephan Müller about 4 years ago
The thing is that the timestamps are 4 seconds apart by default, which results in an float at the end.
Updated by Stephan Müller about 4 years ago
I think the following should fix the problem:
diff --git a/src/pybind/mgr/dashboard/frontend/src/app/shared/datatable/table/table.component.html b/src/pybind/mgr/dashboard/frontend/src/app/shared/datatable/table/table.component.html index c985616d3a..ceef88337a 100644 --- a/src/pybind/mgr/dashboard/frontend/src/app/shared/datatable/table/table.component.html +++ b/src/pybind/mgr/dashboard/frontend/src/app/shared/datatable/table/table.component.html @@ -254,7 +254,7 @@ <ng-template #perSecondTpl let-row="row" let-value="value"> - {{ value }} /s + {{ value | dimless }} /s </ng-template> <ng-template #executingTpl
Updated by anurag bandhu about 4 years ago
- Status changed from New to Pending Backport
Updated by anurag bandhu about 4 years ago
- Copied to Backport #44639: nautilus: mgr/dashboard: Pool read/write OPS shows too many decimal places added
Updated by Nathan Cutler about 4 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 137 to Component - Pools
Actions