Cleanup #49236
mgr/dashboard: avoid data processing in crush-map component
Status:
Pending Backport
Priority:
Normal
Assignee:
Category:
General
Target version:
% Done:
0%
Tags:
Backport:
pacific
Reviewed:
Affected Versions:
Pull request ID:
Related issues
History
#1 Updated by Avan Thakkar 3 months ago
- Related to Bug #48922: mgr/dashboard: crush map viewer tables values not reloading automatically added
#2 Updated by Ernesto Puerta 3 months ago
- Status changed from New to In Progress
- Assignee set to Avan Thakkar
- Target version changed from v16.1.1 to v17.0.0
#3 Updated by Ernesto Puerta 22 days ago
- Project changed from mgr to Dashboard
- Category changed from dashboard/general to General
#4 Updated by Avan Thakkar 3 days ago
- Pull request ID set to 40311
#5 Updated by Ernesto Puerta about 20 hours ago
- Status changed from In Progress to Resolved
#6 Updated by Avan Thakkar about 18 hours 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.
#7 Updated by Avan Thakkar about 18 hours ago
- Status changed from Resolved to Pending Backport
- Backport set to pacific
#8 Updated by Backport Bot about 18 hours ago
- Copied to Backport #50680: pacific: mgr/dashboard: avoid data processing in crush-map component added
#9 Updated by Ernesto Puerta about 17 hours 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!