Actions
Cleanup #49236
closedmgr/dashboard: avoid data processing in crush-map component
% Done:
0%
Tags:
Backport:
pacific
Reviewed:
Affected Versions:
Pull request ID:
Updated by Avan Thakkar about 3 years ago
- Related to Bug #48922: mgr/dashboard: crush map viewer tables values not reloading automatically added
Updated by Ernesto Puerta about 3 years ago
- Status changed from New to In Progress
- Assignee set to Avan Thakkar
- Target version changed from v16.1.1 to v17.0.0
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 132 to General
Updated by Ernesto Puerta about 3 years ago
- Status changed from In Progress to Resolved
Updated by Avan Thakkar about 3 years ago
I think this should be backprted to pacific, as crushmap component has the same flaky test in pacific as well which will get fixed by the PR.
Updated by Avan Thakkar about 3 years ago
- Status changed from Resolved to Pending Backport
- Backport set to pacific
Updated by Backport Bot about 3 years ago
- Copied to Backport #50680: pacific: mgr/dashboard: avoid data processing in crush-map component added
Updated by Ernesto Puerta about 3 years ago
Avan Thakkar wrote:
I think this should be backprted to pacific, as crushmap component has the same flaky test in pacific as well which will get fixed by the PR.
I wasn't sure about the backporting as it's a cleanup but if we improve testability in pacific, I'm ok!
Updated by Ernesto Puerta almost 3 years ago
- Status changed from Pending Backport to Resolved
Actions