Dear Team,

I installed Openstack Wallaby using kolla-ansible.

Everything is fine except for the hacluster_corosync container stuck in restarting.

Below are the corosync logs. Has anyone faced this issue before ?

I have two controllers but this issue is on happening on one 

Jan 30 08:19:42 [7] controller1 corosync info    [TOTEM ] kronosnet crypto initialized: aes256/sha384
Jan 30 08:19:42 [7] controller1 corosync info    [TOTEM ] totemknet initialized
Jan 30 08:19:42 [7] controller1 corosync info    [KNET  ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Jan 30 08:19:42 [7] controller1 corosync notice  [SERV  ] Service engine loaded: corosync configuration map access [0]
Jan 30 08:19:42 [7] controller1 corosync info    [QB    ] server name: cmap
Jan 30 08:19:42 [7] controller1 corosync error   [QB    ] Could not bind AF_UNIX (): Address already in use (98)
Jan 30 08:19:42 [7] controller1 corosync info    [QB    ] withdrawing server sockets
Jan 30 08:19:42 [7] controller1 corosync error   [MAIN  ] Can't initialize IPC
Jan 30 08:19:42 [7] controller1 corosync error   [SERV  ] Service engine 'corosync_cmap' failed to load for reason 'qb_ipcs_run error'
Jan 30 08:19:42 [7] controller1 corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.
Jan 30 08:20:43 [7] controller1 corosync notice  [MAIN  ] Corosync Cluster Engine 3.0.3 starting up
Jan 30 08:20:43 [7] controller1 corosync info    [MAIN  ] Corosync built-in features: dbus monitoring watchdog augeas systemd xmlconf vqsim nozzle snmp pie relro bindnow
Jan 30 08:20:43 [7] controller1 corosync warning [MAIN  ] Could not increase RLIMIT_MEMLOCK, not locking memory: Operation not permitted (1)
Jan 30 08:20:43 [7] controller1 corosync notice  [TOTEM ] Initializing transport (Kronosnet).
Jan 30 08:20:43 [7] controller1 corosync info    [TOTEM ] kronosnet crypto initialized: aes256/sha384
Jan 30 08:20:43 [7] controller1 corosync info    [TOTEM ] totemknet initialized
Jan 30 08:20:43 [7] controller1 corosync info    [KNET  ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Jan 30 08:20:43 [7] controller1 corosync notice  [SERV  ] Service engine loaded: corosync configuration map access [0]
Jan 30 08:20:43 [7] controller1 corosync info    [QB    ] server name: cmap
Jan 30 08:20:43 [7] controller1 corosync error   [QB    ] Could not bind AF_UNIX (): Address already in use (98)
Jan 30 08:20:43 [7] controller1 corosync info    [QB    ] withdrawing server sockets
Jan 30 08:20:43 [7] controller1 corosync error   [MAIN  ] Can't initialize IPC
Jan 30 08:20:43 [7] controller1 corosync error   [SERV  ] Service engine 'corosync_cmap' failed to load for reason 'qb_ipcs_run error'
Jan 30 08:20:43 [7] controller1 corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.
Jan 30 08:21:43 [7] controller1 corosync notice  [MAIN  ] Corosync Cluster Engine 3.0.3 starting up
Jan 30 08:21:43 [7] controller1 corosync info    [MAIN  ] Corosync built-in features: dbus monitoring watchdog augeas systemd xmlconf vqsim nozzle snmp pie relro bindnow
Jan 30 08:21:43 [7] controller1 corosync warning [MAIN  ] Could not increase RLIMIT_MEMLOCK, not locking memory: Operation not permitted (1)
Jan 30 08:21:43 [7] controller1 corosync notice  [TOTEM ] Initializing transport (Kronosnet).
Jan 30 08:21:44 [7] controller1 corosync info    [TOTEM ] kronosnet crypto initialized: aes256/sha384
Jan 30 08:21:44 [7] controller1 corosync info    [TOTEM ] totemknet initialized
Jan 30 08:21:44 [7] controller1 corosync info    [KNET  ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Jan 30 08:21:44 [7] controller1 corosync notice  [SERV  ] Service engine loaded: corosync configuration map access [0]
Jan 30 08:21:44 [7] controller1 corosync info    [QB    ] server name: cmap
Jan 30 08:21:44 [7] controller1 corosync error   [QB    ] Could not bind AF_UNIX (): Address already in use (98)
Jan 30 08:21:44 [7] controller1 corosync info    [QB    ] withdrawing server sockets
Jan 30 08:21:44 [7] controller1 corosync error   [MAIN  ] Can't initialize IPC
Jan 30 08:21:44 [7] controller1 corosync error   [SERV  ] Service engine 'corosync_cmap' failed to load for reason 'qb_ipcs_run error'
Jan 30 08:21:44 [7] controller1 corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.