Actions
Bug #42249
closedpg_autoscaler: pool id key not present when completing event
Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
2019-10-09T18:54:14.828 INFO:tasks.ceph.mgr.x.smithi141.stderr:2019-10-09T18:54:14.833+0000 7f61b2d84700 -1 log_channel(cluster) log [ERR] : Unhandled exception from module 'pg_autoscaler' while running on mgr.x: (1,) 2019-10-09T18:54:14.828 INFO:tasks.ceph.mgr.x.smithi141.stderr:2019-10-09T18:54:14.833+0000 7f61b2d84700 -1 pg_autoscaler.serve: 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr:2019-10-09T18:54:14.833+0000 7f61b2d84700 -1 Traceback (most recent call last): 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 175, in serve 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr: self._update_progress_events() 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr: File "/usr/share/ceph/mgr/pg_autoscaler/module.py", line 353, in _update_progress_events 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr: pool_data = pools[int(pool_id)] 2019-10-09T18:54:14.829 INFO:tasks.ceph.mgr.x.smithi141.stderr:KeyError: (1,)
/a/sage-2019-10-09_16:16:16-rados-wip-sage2-testing-2019-10-09-0759-distro-basic-smithi/4372210
Updated by Sage Weil over 4 years ago
- Status changed from New to Fix Under Review
- Priority changed from Normal to Urgent
- Pull request ID set to 30819
Updated by Sebastian Wagner over 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to nautilus
Sage, does this need a backport to Nautilus?
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42551: nautilus: pg_autoscaler: pool id key not present when completing event 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