Project

General

Profile

Actions

Bug #23037

closed

mgr not reporting when ports conflict

Added by CEDRIC VAN FRACHEM about 6 years ago. Updated about 6 years ago.

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

0%

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

Description

After cluster migration from Jevel 10.2.9-0ubuntu0.16.04.1 to Luminous 12.2.2-1xenial on an Ubuntu.16.04.3 LTS (amd64)

ceph df --detail produces no list of pools, although "ceph osd pool ls" provides accurate list of pools.

$ ceph --cluster main osd pool ls
mytenant-data
newtenant-data

$ ceph --cluster main df detail
GLOBAL:
SIZE AVAIL RAW USED %RAW USED OBJECTS
0 0 0 0 0
POOLS:
NAME ID QUOTA OBJECTS QUOTA BYTES USED %USED MAX AVAIL OBJECTS DIRTY READ WRITE RAW USED

$ ceph --cluster main status
cluster:
id: b5ee2a02-b92c-4829-8d43-0eb17314c0f9
health: HEALTH_WARN
no active mgr

services:
mon: 3 daemons, quorum 0,2,1
mgr: no daemons active
osd: 3 osds: 3 up, 3 in
data:
pools: 0 pools, 0 pgs
objects: 0 objects, 0 bytes
usage: 0 kB used, 0 kB / 0 kB avail
pgs:

The problem is not observed when deploying same packages/system configuration with a blank cluster (offline, debian-based deployment using an up-to-date 16.04 apt mirror with luminous .debs)


Related issues 1 (0 open1 closed)

Copied to mgr - Backport #23175: luminous: mgr not reporting when ports conflictResolvedPrashant DActions
Actions #1

Updated by CEDRIC VAN FRACHEM about 6 years ago

Problem is not related to migration, but to behaviour of the new manager. When a manager and OSD instance run on the same system, and if the allowed port ranges overlap, then it can occur that the OSD starts first, preventing the manager to bind on the same port. BUT in this case, the manager does not rebind on an other port, and we have the described behaviour.

Actions #2

Updated by Josh Durgin about 6 years ago

  • Project changed from Ceph to mgr
  • Subject changed from Empty df detail after migrating from Jewel to Luminous to mgr not reporting when ports conflict
  • Category deleted (ceph cli)
Actions #3

Updated by John Spray about 6 years ago

  • Status changed from New to In Progress
  • Assignee set to John Spray

Confirmed, the DaemonServer.init errors are not being handled :-o

All the other daemons seem to do an exit(1) on bind failures, so I guess we will too.

Actions #4

Updated by John Spray about 6 years ago

  • Status changed from In Progress to Fix Under Review
  • Assignee deleted (John Spray)
  • Backport set to luminous
Actions #5

Updated by Kefu Chai about 6 years ago

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

Updated by Nathan Cutler about 6 years ago

  • Copied to Backport #23175: luminous: mgr not reporting when ports conflict added
Actions #7

Updated by Nathan Cutler about 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF