Bug #43765
mgr/dashboard: Dashboard breaks on the selection of a bad pool
Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/pools
Target version:
% Done:
0%
Source:
Tags:
Backport:
octopus nautilus
Regression:
No
Severity:
3 - minor
Description
If a pool is created with a wrong rule that is oversized for the cluster it gets into the "creating+incomplete" state.
This wont break the dashboard yet, but when clicking on the pool to get it's details every API request will be left unanswerd. The first unanswered call is "/api/pool/$badPool/configuration".
To reproduce this you can create an erasure code profile with a greater value for k than you have OSDs.
Related issues
History
#1 Updated by Stephan Müller about 1 year ago
- Related to Bug #43771: pybind/rbd: config_list hangs if given an pool with a bad pg state added
#2 Updated by Stephan Müller about 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 32829
#3 Updated by Stephan Müller about 1 year ago
- Backport set to nautilus
#4 Updated by Stephan Müller about 1 year ago
- Related to Bug #44224: mgr/dashboard: Timeouts for rbd.py calls added
#5 Updated by Alfonso Martínez 10 months ago
- Backport changed from nautilus to octopus nautilus
#6 Updated by Lenz Grimmer 10 months ago
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
#7 Updated by Nathan Cutler 10 months ago
- Copied to Backport #45557: octopus: mgr/dashboard: Dashboard breaks on the selection of a bad pool added
#8 Updated by Nathan Cutler 10 months ago
- Copied to Backport #45558: nautilus: mgr/dashboard: Dashboard breaks on the selection of a bad pool added
#9 Updated by Lenz Grimmer 8 months ago
- Status changed from Pending Backport to Resolved