Actions
Bug #41878
closedmgr/prometheus: KeyError in mgr/prometheus/module.py", line 490, in get_mgr_status
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
prometheus module
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
https://github.com/rook/rook/issues/3873
[16/Sep/2019:14:44:34] HTTP Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cherrypy/_cprequest.py", line 656, in respond response.body = self.handler() File "/usr/lib/python2.7/site-packages/cherrypy/lib/encoding.py", line 188, in __call__ self.body = self.oldhandler(*args, **kwargs) File "/usr/lib/python2.7/site-packages/cherrypy/_cpdispatch.py", line 34, in __call__ return self.callable(*self.args, **self.kwargs) File "/usr/share/ceph/mgr/prometheus/module.py", line 1054, in metrics return self._metrics(instance) File "/usr/share/ceph/mgr/prometheus/module.py", line 1068, in _metrics instance.collect_cache = instance.collect() File "/usr/share/ceph/mgr/prometheus/module.py", line 918, in collect self.get_mgr_status() File "/usr/share/ceph/mgr/prometheus/module.py", line 490, in get_mgr_status always_on_modules = mgr_map['always_on_modules'][ceph_release] KeyError: 'mimic'
mgr and mons are on 14.2.4 already, 2 of the OSDs as well. The remaining bits not yet. This is the condition this is happening in.
Rook issue: https://github.com/rook/rook/issues/3873
Updated by Sebastian Wagner over 4 years ago
- Status changed from New to Fix Under Review
Updated by Sebastian Wagner over 4 years ago
- Related to Bug #41740: mgr/dashboard: After upgrade, dashboard still shows old version sometimes added
Updated by Sebastian Wagner over 4 years ago
#41740 might be the root cause of this issue.
Updated by Sebastian Wagner over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42144: nautilus: mgr/prometheus: KeyError in mgr/prometheus/module.py", line 490, in get_mgr_status added
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