Resource: res_masakari_4cc6744_vip not running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Masakari Charm |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
I used to deploy an Openstack bundle including Masakari for monthes but since Charmed Openstack 21.04, everytime I deploy Masakari, I get this message : Resource: res_masakari_
and the VIP is not coming up (the service itself seems to work properly though, curling the haproxy target endpoint gives an answer).
Here is a snipet of my masakari configuration :
=======
series: focal
applications:
masakari:
charm: cs:masakari-11
channel: stable
num_units: 3
to:
- lxd:3
- lxd:4
- lxd:5
options:
debug: false
evacuatio
openstack
use-
use-syslog: false
verbose: false
vip: 192.168.111.225
worker-
masakari-
charm: cs:hacluster-76
channel: stable
options:
cluster_
maas_
maas_url: http://<MAAS-IP>:5240/MAAS
masakari-
charm: cs:masakari-
channel: stable
masakari-
charm: cs:mysql-router-10
channel: stable
masakari-
charm: cs:pacemaker-
channel: stable
options:
enable-
enable-
relations:
- - masakari:ha
- masakari-
- - nova-compute:
- masakari-
- - masakari-
- masakari-
- - nova-compute:
- masakari-
- - keystone:
- masakari-
- - masakari-
- vault:certificates
- - masakari:
- keystone:
- - masakari:shared-db
- masakari-
- - masakari-
- mysql-innodb-
- - masakari:amqp
- rabbitmq-
- - masakari:
- vault:certificates
=======
For what I can tell, pacemaker is stuck on the masakari-hacluster units but also on the nova-compute units.
Here is a snippet of /var/log/
=======
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (crm_timer_popped) info: Cluster Recheck Timer just popped | input=I_PE_CALC time=60000ms
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_state_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_state_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_state_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_te_invoke) info: Processing graph 21 (ref=pe_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (te_fence_node) notice: Requesting fencing (reboot) of node node1 | action=39 timeout=60000
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (handle_request) notice: Client pacemaker-
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (initiate_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (can_fence_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (process_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (process_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (dynamic_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (process_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (process_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (stonith_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (call_remote_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (call_remote_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-fenced [548] (remote_op_done) error: Operation 'reboot' targeting node1 on <no-one> for <email address hidden>: No such device
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (tengine_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (tengine_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (tengine_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (abort_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (tengine_
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (run_graph) notice: Transition 21 (Complete=2, Pending=0, Fired=0, Skipped=0, Incomplete=27, Source=
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_log) info: Input I_TE_SUCCESS received in state S_TRANSITION_ENGINE from notify_crmd
Jul 13 15:24:13 juju-5073fb-3-lxd-7 pacemaker-controld [553] (do_state_
=======
And here is a snippet of pacemaker.log on masakari-
=======
Set r/w permissions for uid=122, gid=127 on /var/log/
Jul 12 16:03:58 lab-vit-worker2 pacemaker-remoted [210996] (crm_log_init) info: Changed active directory to /var/lib/
Jul 12 16:03:58 lab-vit-worker2 pacemaker-remoted [210996] (main) notice: Starting Pacemaker remote executor
Jul 12 16:03:58 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:58 lab-vit-worker2 pacemaker-remoted [210996] (pcmk__init_tls_dh) info: Generating Diffie-Hellman parameters with 2048-bit prime for TLS
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:03:59 lab-vit-worker2 pacemaker-remoted [210996] (main) notice: Pacemaker remote executor successfully started and accepting connections
Jul 12 16:04:38 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_rw because not connected to cluster
Jul 12 16:04:38 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:05:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:05:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:05:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:05:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:06:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:06:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:06:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:06:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:07:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:07:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:07:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:07:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:08:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:08:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:08:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:08:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:09:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:09:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:09:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:09:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:10:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:10:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:10:40 lab-vit-worker2 pacemaker-remoted [210996] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:10:40 lab-vit-worker2 pacemaker-remoted [210996] (handle_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (crm_signal_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (lrmd_exit) info: Terminating with 0 clients
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [210996] (crm_xml_cleanup) info: Cleaning up memory from libxml2
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (crm_log_init) info: Changed active directory to /var/lib/
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (main) notice: Starting Pacemaker remote executor
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (pcmk__init_tls_dh) info: Generating Diffie-Hellman parameters with 2048-bit prime for TLS
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (qb_ipcs_
Jul 12 16:11:23 lab-vit-worker2 pacemaker-remoted [226614] (main) notice: Pacemaker remote executor successfully started and accepting connections
Jul 12 16:11:40 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:11:40 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:11:40 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:11:40 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:12:40 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:12:40 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:12:40 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:12:40 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:13:41 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:13:41 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:13:41 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:13:41 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:14:41 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 12 16:14:41 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:14:41 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 12 16:14:41 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 12 16:14:58 lab-vit-worker2 pacemaker-remoted [226614] (crm_remote_accept) info: New remote connection from ::ffff:
Jul 12 16:14:58 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (remoted_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (process_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (process_
Jul 12 16:14:59 IPaddr2(
Jul 12 16:14:59 IPaddr2(
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (process_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (process_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (process_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (log_execute) info: executing - rsc:res_
Jul 12 16:14:59 lab-vit-worker2 pacemaker-remoted [226614] (log_finished) info: finished - rsc:res_
Jul 12 16:18:08 lab-vit-worker2 pacemaker-remoted [226614] (crm_remote_accept) info: New remote connection from ::ffff:
Jul 12 16:18:08 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 12 16:18:08 lab-vit-worker2 pacemaker-remoted [226614] (remoted_
Jul 12 16:18:10 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 12 16:18:10 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:45:57 lab-vit-worker2 pacemaker-remoted [226614] (crm_remote_accept) info: New remote connection from ::ffff:
Jul 13 07:45:57 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:45:58 lab-vit-worker2 pacemaker-remoted [226614] (remoted_
Jul 13 07:46:36 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:46:36 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:46:36 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:46:36 lab-vit-worker2 pacemaker-remoted [226614] (lrmd_remote_
Jul 13 07:47:24 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 13 07:47:24 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:47:24 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 13 07:47:24 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:48:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 13 07:48:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:48:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 13 07:48:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:49:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 13 07:49:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:49:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 13 07:49:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:50:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
Jul 13 07:50:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:50:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to cib_ro because not connected to cluster
Jul 13 07:50:25 lab-vit-worker2 pacemaker-remoted [226614] (handle_
Jul 13 07:51:25 lab-vit-worker2 pacemaker-remoted [226614] (ipc_proxy_accept) warning: Cannot proxy IPC connection from uid 0 gid 0 to stonith-ng because not connected to cluster
=======
I'm no corosync/pacemaker expert but there seem to be an issue somewhere around that.
As MaaS is used as a fencing device, I checked that MaaS is accessible from every pacemaker units and this is the case.
I have no more ideas on what to check/try.
Is it due to some misconfiguration in my deployment ?
Best regards