Actions
Bug #42017
closedmgr/prometheus: UnboundLocalError occurs when obj_store is neither filestore nor bluestore
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus, mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Failed to view metrics through browser when obj_store is neither filestore nor bluestore. The error message is as follows.
if osd_dev_node and osd_dev_node == "unknown":
UnboundLocalError: local variable 'osd_dev_node' referenced before assignment
Updated by Jan Fajerski over 4 years ago
- Status changed from New to Pending Backport
- Backport set to nautilus, mimic
Updated by Jan Fajerski over 4 years ago
- Copied to Backport #42765: mimic: mgr/prometheus: UnboundLocalError occurs when obj_store is neither filestore nor bluestore added
Updated by Jan Fajerski over 4 years ago
- Copied to Backport #42766: nautilus: mgr/prometheus: UnboundLocalError occurs when obj_store is neither filestore nor bluestore added
Updated by Konstantin Shalygin over 4 years ago
- Backport changed from nautilus, mimic to nautilus, mimic, luminous
Updated by Konstantin Shalygin over 4 years ago
- Copied to Backport #42784: luminous: mgr/prometheus: UnboundLocalError occurs when obj_store is neither filestore nor bluestore added
Updated by Yuri Weinstein over 4 years ago
Updated by Nathan Cutler over 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".
Actions