fuel 5.1.1 - Galera Cluster node failure and Cloud down.
Bug #1428133 reported by
Vasilios Tzanoudakis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Library (Deprecated) | ||
5.0.x |
Invalid
|
High
|
Fuel Library (Deprecated) | ||
5.1.x |
Invalid
|
High
|
MOS Maintenance | ||
6.0.x |
Invalid
|
High
|
MOS Maintenance | ||
6.1.x |
Invalid
|
High
|
Fuel Library (Deprecated) |
Bug Description
Enviroment:
3 Controllers HA + Ceilometer
Ubuntu OS
Ceph for ALL
GRE
ISO used: fuel-community-
Here are the logs from mysql : http://
The problem in the cloud started on :Mar 4 00:54:55.
At this time the l3 agent wasn't responding and I lost l3 connectivity for all instances.
Pacemaker timed out after some retries trying to bring the mysql up again.
What i have done as a quick fix.
1. Restarted the node that had mysql server instance down.
2. Restarted the l3 agent resource from crm.
Is this someking of galera/mysql bug?
thank you
Guys after many hours of digging around I have found that the node crash had to do with innobackupex lock.
check this out.
https:/ /bugs.launchpad .net/percona- xtradb- cluster/ +bug/1401133
http:// www.percona. com/forums/ questions- discussions/ percona- xtrabackup/ 31893-innobacku pex-crashing- percona- server- 5-6-21- 70-1