I've done a bit more testing, and here are my observations:
1) rebooting a container internally/stop-start externally using lxc-*
Works OK - container re-joins the corosync cluster just fine.
2) rebooting the physical host
Fails - containers never re-join the corosync cluster and perform the configured isolation response which is to stop everything.
That said, if I reconfigure the cluster to using a new multicast address, the cluster reforms OK.
So it would appear that cross server multicast is not being restored on a physical server reboot; I guess this could be something todo with switch configuration as well.
I've done a bit more testing, and here are my observations:
1) rebooting a container internally/ stop-start externally using lxc-*
Works OK - container re-joins the corosync cluster just fine.
2) rebooting the physical host
Fails - containers never re-join the corosync cluster and perform the configured isolation response which is to stop everything.
That said, if I reconfigure the cluster to using a new multicast address, the cluster reforms OK.
So it would appear that cross server multicast is not being restored on a physical server reboot; I guess this could be something todo with switch configuration as well.