c. On the mysql units I could observe a similar pattern as yesterday, after ~10min I could see the HA VIP on mysql/0 https://pastebin.canonical.com/132916/
d. However! After another ~10mins the mysql service partially recovered, mysql/0 got it's proper ip back. Still the mysql-hacluster subordinate still was down, and the config-changed hook hung:
'''2015-06-10 08:43:35 INFO juju.utils.fslock fslock.go:146 attempted lock failed "uniter-hook-execution", mysql/0: running hook config-changed, currently held: mysql-hacluster/1: running hook "config-changed"'''
This didn't change after 1h+
e. Also, the keystone service had the similar issues after 1h+, ie. the HA VIP on keystone/1; note the agent-versions: https://pastebin.canonical.com/132926/
I've dumped /var/lib and /var/log from machines-{1,2,3} and can make them available.
I failed to mention yesterday that keystone and possibly other
HA-ified services had similar issues as mysql.
Also, I've retried an upgrade today:
a. Upgrading from 1.20.14 --> 1.22.5.
b. Issue lp:1441478 struck again
c. On the mysql units I could observe a similar pattern as yesterday, after ~10min I could see the HA VIP on mysql/0 https:/ /pastebin. canonical. com/132916/
d. However! After another ~10mins the mysql service partially recovered, mysql/0 got it's proper ip back. Still the mysql-hacluster subordinate still was down, and the config-changed hook hung: hook-execution" , mysql/0: running hook config-changed, currently held: mysql-hacluster/1: running hook "config-changed"'''
'''2015-06-10 08:43:35 INFO juju.utils.fslock fslock.go:146 attempted lock failed "uniter-
This didn't change after 1h+
e. Also, the keystone service had the similar issues after 1h+, ie. the HA VIP on keystone/1; note the agent-versions: https:/ /pastebin. canonical. com/132926/
I've dumped /var/lib and /var/log from machines-{1,2,3} and can make them available.