Hi James,
Thanks for looking into this. Here is the steps to reproduce the issue:
1. Deploy service (ex, mysql) to 3 of physical nodes by using Juju. -> OK
2. Deploy trusty/hacluster-18 -> OK
3. Hook up relation between mysql – hacluster -> Hookup failed.
4. Use “juju resolved –retry” command to fix issue -> no help. Still shows red line.
5. Login to one of physical node to run a check.
a. Verify the corosync & pacemaker status -> both of services not start
b. Verify corosync.conf -> mysql HA setting hasn’t been written to this file.
c. Run “sudo crm_mon” -> connection refused. Node cluster failed.
*I can also reproduce the issue by following the steps:
Mine step was:
1. bootstrap 2. juju deploy -n 3 -constrains tags=physical keystone 3. juju deploy hacluster hacluster-keystone 4. juju add-relation hacluster-keystone keystone
juju stat keystone gives: http://paste.ubuntu.com/10790371/
even if I deploy services to the container, the hooks will fail as well.
Attach logs for analysis
Hi James,
Thanks for looking into this. Here is the steps to reproduce the issue:
1. Deploy service (ex, mysql) to 3 of physical nodes by using Juju. -> OK
2. Deploy trusty/hacluster-18 -> OK
3. Hook up relation between mysql – hacluster -> Hookup failed.
4. Use “juju resolved –retry” command to fix issue -> no help. Still shows red line.
5. Login to one of physical node to run a check.
a. Verify the corosync & pacemaker status -> both of services not start
b. Verify corosync.conf -> mysql HA setting hasn’t been written to this file.
c. Run “sudo crm_mon” -> connection refused. Node cluster failed.
*I can also reproduce the issue by following the steps:
Mine step was:
1. bootstrap
2. juju deploy -n 3 -constrains tags=physical keystone
3. juju deploy hacluster hacluster-keystone
4. juju add-relation hacluster-keystone keystone
juju stat keystone gives: paste.ubuntu. com/10790371/
http://
even if I deploy services to the container, the hooks will fail as well.
Attach logs for analysis