Fix for Issue 65

[RealLukeMartin]

getvalkyrie.mysql role consistently failed when attempting to build a new valkyrie box more info here https://github.com/GetValkyrie/valkyrie/issues/65

I switched out the GetValkyrie/ansible-role-mysql back to geerlingguy/ansible-role-mysql and pinned the submodule to the 1.5.2 release. The box built smooth and successfully, front end came up on the first request as well.

[ergonlogic]

@RealLukeMartin Feel free to merge these fixes.

[niccolox]

I get this mysql error now

==> valkyrie: TASK: [getvalkyrie.mysql | Update MySQL root password for localhost root account.] * ==> valkyrie: failed: [localhost] => (item=valkyrie) => {"failed": true, "item": "valkyrie"} ==> valkyrie: msg: unsupported parameter for module: config_file ==> valkyrie: failed: [localhost] => (item=127.0.0.1) => {"failed": true, "item": "127.0.0.1"} ==> valkyrie: msg: unsupported parameter for module: config_file ==> valkyrie: failed: [localhost] => (item=::1) => {"failed": true, "item": "::1"} ==> valkyrie: msg: unsupported parameter for module: config_file ==> valkyrie: failed: [localhost] => (item=localhost) => {"failed": true, "item": "localhost"} ==> valkyrie: msg: unsupported parameter for module: config_file ==> valkyrie: ==> valkyrie: FATAL: all hosts have already failed -- aborting ==> valkyrie: ==> valkyrie: PLAY RECAP ****** ==> valkyrie: to retry, use: --limit @/root/site.retry ==> valkyrie: ==> valkyrie: localhost : ok=12 changed=6 unreachable=0 failed=1
The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what

[RealLukeMartin]

It should be using the geerlingguy.mysql role now instead of getvalkyrie.mysql after the merge. Did you do a pull after this merge a few minutes ago?

[niccolox]

yes

[niccolox]

I used the old project need to do another vnew