Hi, guys. I am also actively testing to reproduce similar issue (that our customer complained about) - I'm deploying three unit percona-cluster (each unit in a separate LXC on separate physical machine) with three unit keystone (both services have hacluster subodinated), but failed to reproduce it so far - we made sure everything is set up correctly, run 'keystone service-list' and similar, did a hard-reset via IPMI of the node where percona-cluster VIP resides, corosync/pacemaker did their job, VIP moved, 'keystone service-list' is happy...
I'll update here with more info as I go along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
