Problem: MySQL service down in AtoM Trusty playbook

[jraddaoui]

We have changed the Ubuntu version check to install the Percona server in artefactual-labs/ansible-percona@16a44e5

After those changes it installs Percona 5.6 by default in Ubuntu Trusty if it's not changed in the playbook using the new mysql_version_major and mysql_version_minor variables.

[hakamine]

@jraddaoui the ansible-percona travis test for trusty passed with the default of 5.6 so this is unexpected 😞. Anything helpful in the error logs?
According to percona lifecycle doc only subscribers get security updates/bug fixes for 5.5 (so having 5.6 working on trusty would be a good thing).

[jraddaoui]

Hi @hakamine ,

In atom-trusty, using Percona 5.6, when the "Purge database" task is reached, MySQL is down:

TASK [artefactual.atom : Purge database] ***************************************
fatal: [atom-local]: FAILED! => {"changed": true, "cmd": ["php", "symfony", "tools:purge", "--no-confirmation", "--email=demo@example.com", "--username=demo", "--password=demo", "--title=AtoM", "--description=Access to Memory", "--url=http://undefined"], "delta": "0:00:02.138478", "end": "2018-05-10 19:02:17.061185", "msg": "non-zero return code", "rc": 1, "start": "2018-05-10 19:02:14.922707", "stderr": "\n                                                                                                                      \n  Unable to open PDO connection [wrapped: SQLSTATE[HY000] [2003] Can't connect to MySQL server on '127.0.0.1' (111)]  \n                                                                                                                      ", "stderr_lines": ["", "                                                                                                                      ", "  Unable to open PDO connection [wrapped: SQLSTATE[HY000] [2003] Can't connect to MySQL server on '127.0.0.1' (111)]  ", "                                                                                                                      "], "stdout": "", "stdout_lines": []}

Here's /var/log/mysql/error.log after that fail, which looks to be a normal shutdown ...

https://gist.github.com/jraddaoui/89543b2d7901e5e72987628cc3cbaaed

[jraddaoui]

And sudo service mysql start does not bring it up and does not add anything to that log.

[hakamine]

@jraddaoui It looks like the problem is not with percona 5.6 but with the playbook running the role ansible-percona-client that installs a 5.5 client, just right after the ansible-percona role installs the 5.6 server. The ansible-percona-client is not required (the ansible-percona role with install both server and client). I created PR #78 with a fix.

[jraddaoui]

That's a lot better, thanks @hakamine!

[jraddaoui]

I've tested in both Vagrant boxes and merged.