Bug #52041
Updated by Sebastian Wagner over 2 years ago
Only one mgr is active, so any mgr module that has an associated listening port should only be listed against the active mgr module. for example in 16.2.5 I see this <pre> [ceph: root@cs8-1 /]# ceph orch ps NAME HOST PORTS STATUS REFRESHED AGE MEM USE MEM LIM VERSION IMAGE ID CONTAINER ID crash.cs8-1 cs8-1 running (13m) 2m ago 13m 6953k - 16.2.5 6933c2a0b7dd 9fa93e9b7f97 crash.cs8-2 cs8-2 running (11m) 9m ago 11m 7117k - 16.2.5 6933c2a0b7dd 2e94894c76e0 crash.cs8-3 cs8-3 running (9m) 9m ago 9m 7134k - 16.2.5 6933c2a0b7dd f3696ee28503 mgr.cs8-1.iugjdk cs8-1 *:9283 running (14m) 2m ago 14m 510M - 16.2.5 6933c2a0b7dd a8c6a3d46bbf mgr.cs8-2.shbjhe cs8-2 *:8443 running (11m) 9m ago 11m 373M - 16.2.5 6933c2a0b7dd 0274bb40824f mon.cs8-1 cs8-1 running (14m) 2m ago 15m 61.7M 2048M 16.2.5 6933c2a0b7dd 3a31bf1bef8a mon.cs8-2 cs8-2 running (11m) 9m ago 10m 55.7M 2048M 16.2.5 6933c2a0b7dd 042612c50e48 mon.cs8-3 cs8-3 running (9m) 9m ago 9m 52.4M 2048M 16.2.5 6933c2a0b7dd 08c86e9e1556 </pre> in this case ports 9283 and 8443 should be shown against the *same* same mgr instance In addition when I deployed with skip-monitoring, mgr/prometheus wasn't enabled but the output in orch ps still showed 9283 against the mgr!