Project

General

Profile

Actions

Bug #42640

closed

pybind/mgr/pg_autoscaler: shutdown method not implemented

Added by Patrick Donnelly over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Urgent
Category:
-
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2019-11-04T17:49:45.048+0000 7fd20de96700 10 mgr shutdown module pg_autoscaler shutdown() returned
2019-11-04T17:49:45.048+0000 7fd20de96700 10 mgr shutdown calling module progress shutdown()
...
2019-11-04T17:49:45.071+0000 7fd20de96700 10 mgr shutdown joining module pg_autoscaler
...
2019-11-04T17:50:00.734+0000 7fd1f7fff700  4 mgr[pg_autoscaler] _maybe_adjust

From: /ceph/teuthology-archive/pdonnell-2019-11-04_12:55:15-fs-wip-pdonnell-testing-20191104.085350-distro-basic-smithi/4472537/remote/smithi134/log/ceph-mgr.y.log.gz

Implementation of the serve method requires implementation of shutdown.

Revealed by fix for #42299.


Related issues 2 (0 open2 closed)

Related to CephFS - Bug #42299: mgr/volumes: cleanup libcephfs handles on mgr shutdownResolvedVenky Shankar

Actions
Copied to mgr - Backport #42695: nautilus: pybind/mgr/pg_autoscaler: shutdown method not implementedResolvedNathan CutlerActions
Actions #1

Updated by Patrick Donnelly over 4 years ago

  • Related to Bug #42299: mgr/volumes: cleanup libcephfs handles on mgr shutdown added
Actions #2

Updated by Patrick Donnelly over 4 years ago

  • Description updated (diff)
Actions #3

Updated by Patrick Donnelly over 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 31398
Actions #4

Updated by Sage Weil over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #42695: nautilus: pybind/mgr/pg_autoscaler: shutdown method not implemented added
Actions #6

Updated by Nathan Cutler about 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

Also available in: Atom PDF