CI ovb-ha job is broken on Galera setup with Puppet4
Bug #1645787 reported by
Emilien Macchi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Emilien Macchi |
Bug Description
Error: Failed to apply catalog: Execution of '/usr/bin/mysql -NBe SELECT CONCAT(User, '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/
When deploying HA scenario with MySQL Galera.
It might be an orchestration issue/ordering.
From this failed CI job [1], it looks like the galera cluster has not been started at all. I don't see _any_ logs from the galera resource agent on any of the controllers. This probably means that the galera resource hasn't been created as expected, or that something prevented pacemaker to enable the galera resource (i.e. start the galera cluster)
For the record, when the galera resource is created under pacemaker, we should see logs like "galera( galera) .*INFO: now attempting to detect last commit version using 'mysqld_safe --wsrep-recover' on all controllers in /var/log/messages mariadb/ mariadb. log would reflect that action with a log like "Running position recovery with.*"
/var/log/
the subsequent DB log always go in /var/log/mysqld.log (mariadb.log is only used for bootstrapping the cluster)