Project

General

Profile

Actions

Bug #57060

closed

cephadm won't deploy mon service, reports wrongly filtered out

Added by Kenneth Waegeman almost 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
cephadm/monitoring
Target version:
-
% Done:

0%

Source:
Community (user)
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

I'm running 17.2.3, but I've seen this in earlier versions too:

cephadm won't apply the mon service,

mon 5/5 10m ago 53m zorua04.zorua.os;zorua05.zorua.os;ceph301.zorua.os;ceph302.zorua.os;ceph303.zorua.os

it reports this:

2022-08-08T14:21:30.758266+0200 mgr.zorua04.mkgxgv [INF] Filtered out host zorua04.zorua.os: does not belong to mon public_network (10.141.15.0/24)
2022-08-08T14:21:30.758472+0200 mgr.zorua04.mkgxgv [INF] Filtered out host zorua05.zorua.os: does not belong to mon public_network (10.141.15.0/24)
2022-08-08T14:21:30.758620+0200 mgr.zorua04.mkgxgv [INF] Filtered out host ceph301.zorua.os: does not belong to mon public_network (10.141.15.0/24)
2022-08-08T14:21:30.758765+0200 mgr.zorua04.mkgxgv [INF] Filtered out host ceph302.zorua.os: does not belong to mon public_network (10.141.15.0/24)
...

and when I change monitors nothing happens, I added/deleted them manually using ceph orch daemon add/rm and that works. The message 'does not belong to mon public_network (10.141.15.0/24)' is false, all hosts are in this network, eg

zorua04.zorua.os. 604800 IN A 10.141.15.4

Thanks!!

Kenneth


Related issues 2 (0 open2 closed)

Related to Orchestrator - Bug #54235: Filtered out host ceph03: does not belong to mon public_networkClosed

Actions
Copied to Orchestrator - Backport #57423: quincy: cephadm won't deploy mon service, reports wrongly filtered outResolvedAdam KingActions
Actions

Also available in: Atom PDF