Bug #44224
mgr/dashboard: Timeouts for rbd.py calls
Status:
New
Priority:
High
Assignee:
-
Category:
General
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
As the corner cases are not implemented in many rbd.py methods, they can fail without a response on a specific pool (mostly bad pools).
If this is implemented remove the workaround that was implemented to fix #43765.
For details what known issue exists see #43771.
For details about the discussion that was made look at the PR that fixed #43765.
Make sure that #43771 is still not addressed before starting with this issue.
For details how this was implemented in openATTIC look here
Related issues
History
#1 Updated by Stephan Müller about 4 years ago
- Description updated (diff)
#2 Updated by Stephan Müller about 4 years ago
- Related to Bug #43771: pybind/rbd: config_list hangs if given an pool with a bad pg state added
#3 Updated by Stephan Müller about 4 years ago
- Related to Bug #43765: mgr/dashboard: Dashboard breaks on the selection of a bad pool added
#4 Updated by Nathan Cutler about 4 years ago
- Duplicated by Bug #44223: mgr/dashboard: Timeouts for rbd.py calls added
#5 Updated by Ernesto Puerta over 3 years ago
- Priority changed from Normal to High
- Severity changed from 3 - minor to 1 - critical
The workaround this fix this issue is behind this flapping Ceph API failure
#6 Updated by Ernesto Puerta over 3 years ago
- Related to Bug #46815: mgr/dashboard: FAIL: test_pool_create (tasks.mgr.dashboard.test_pool.PoolTest) added
#7 Updated by Lenz Grimmer over 3 years ago
Per today's discussion in the backlog grooming call, this might be solvable by reducing a timeout value here?
#8 Updated by Ernesto Puerta almost 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 132 to General