Project

General

Profile

Actions

Bug #57651

closed

cephadm: serve loop just loops forever if migration_current is too high

Added by Adam King over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

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

Description

cephadm uses the config option mgr/cephadm/migration_current to track it doing a set of migration steps. In normal operation this works fine, but if something happens that causes the setting to be set higher than whatever the last migration is defined to be at that point (either a user setting the value to something it shouldn't be, or somebody using cephadm trying to downgrade the manager), the serve loop will just loop forever without actually accomplishing anything as it thinks migrations are "in progress".


Related issues 2 (0 open2 closed)

Copied to Orchestrator - Backport #58205: quincy: cephadm: serve loop just loops forever if migration_current is too highResolvedAdam KingActions
Copied to Orchestrator - Backport #58206: pacific: cephadm: serve loop just loops forever if migration_current is too highResolvedAdam KingActions
Actions #1

Updated by Michael Fritch over 1 year ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 48213
Actions #2

Updated by Adam King over 1 year ago

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

Updated by Backport Bot over 1 year ago

  • Copied to Backport #58205: quincy: cephadm: serve loop just loops forever if migration_current is too high added
Actions #4

Updated by Backport Bot over 1 year ago

  • Copied to Backport #58206: pacific: cephadm: serve loop just loops forever if migration_current is too high added
Actions #5

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions #6

Updated by Adam King about 1 year ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF