rook: The ip address of rook-ceph mgr pod is always in blocklist
version
rook_ceph:v1.12.11
ceph:v17.2.6
As shown below, the ip address of the mgr-b pod is 10.96.9.10
rook-ceph-mgr-b-6d5b7cf6bb-lj9b7 3/3 Running 0 20m 10.96.9.10 a6000-4 <none> <none>
As shown below, only the mgr-b pod ip is listed in the blocklist,no matter which node mgr-b is started on
ceph osd blocklist ls
10.96.9.10:0/2508813557 2024-07-10T08:31:08.883360+0000
10.96.9.10:0/120580002 2024-07-10T08:31:08.883360+0000
10.96.9.10:0/2868010900 2024-07-10T08:31:08.883360+0000
10.96.9.10:0/1399480183 2024-07-10T08:31:08.883360+0000
10.96.9.10:6801/2258748430 2024-07-10T08:31:08.883360+0000
10.96.9.10:6800/2258748430 2024-07-10T08:31:08.883360+0000
listed 6 entries
ceph health status
ceph -s
cluster:
id: xxxxxx
health: HEALTH_OK
services:
mon: 5 daemons, quorum a,b,c,d,g (age 38m)
mgr: b(active, since 3m), standbys: a
mds: 5/5 daemons up, 5 hot standby
......
mgr pod log file mgr-b.log
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 25 (8 by maintainers)
It is RBD – just the part that is running in
rbd_supportmanager module. This includes:rbd taskcommands (the manager running long-running maintenance operations on RBD images such as flattening on behalf of the user)rbd perfcommands (the manager registering OSD perf queries)cc @ajarr