I hit this bug too, both in the form mentioned in the report and in the one mentioned by Sean in comment #6.
In the first case the problem was that the host was running a Mysql server instance and therefore the mariadb container was not happy about it. Root case for this problem was PEBCAK. The problem was identified by simply running:
docker logs mariadb
Then the error in the 2nd form appeared.
failed: [localhost] => {"attempts": 10, "changed": false, "cmd": ["docker", "exec", "-t", "kolla_ansible", "/usr/bin/ansible", "localhost", "-m", "mysql_user", "-a", "login_host='10.127.1.6' login_port='3306' login_user='root' login_password='password' name='haproxy' password='' host='%'"], "delta": "0:00:00.705690", "end": "2015-11-18 06:57:47.981298", "failed": true, "rc": 2, "start": "2015-11-18 06:57:47.275608", "stdout_lines": ["localhost | FAILED! => {", " \"changed\": false, ", " \"failed\": true, ", " \"msg\": \"unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: (1130, \\\"Host 'host-10-127-1-6.openstacklocal' is not allowed to connect to this MariaDB server\\\")\"", "}"], "warnings": []}
stdout: localhost | FAILED! => {
"changed": false,
"failed": true,
"msg": "unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: (1130, \"Host 'host-10-127-1-6.openstacklocal' is not allowed to connect to this MariaDB server\")"
}
However, right before that I noticed that:
TASK: [mariadb | Sleeping for 15 seconds while the cluster starts] ************
skipping: [localhost]
This step should have probably not been skipped since the cluster needed actually to be started.
Anyway I worked around the issue in this way:
I hit this bug too, both in the form mentioned in the report and in the one mentioned by Sean in comment #6.
In the first case the problem was that the host was running a Mysql server instance and therefore the mariadb container was not happy about it. Root case for this problem was PEBCAK. The problem was identified by simply running:
docker logs mariadb
Then the error in the 2nd form appeared.
failed: [localhost] => {"attempts": 10, "changed": false, "cmd": ["docker", "exec", "-t", "kolla_ansible", "/usr/bin/ansible", "localhost", "-m", "mysql_user", "-a", "login_ host='10. 127.1.6' login_port='3306' login_user='root' login_password= 'password' name='haproxy' password='' host='%'"], "delta": "0:00:00.705690", "end": "2015-11-18 06:57:47.981298", "failed": true, "rc": 2, "start": "2015-11-18 06:57:47.275608", "stdout_lines": ["localhost | FAILED! => {", " \"changed\": false, ", " \"failed\": true, ", " \"msg\": \"unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: (1130, \\\"Host 'host-10- 127-1-6. openstacklocal' is not allowed to connect to this MariaDB server\\\")\"", "}"], "warnings": []} 127-1-6. openstacklocal' is not allowed to connect to this MariaDB server\")"
stdout: localhost | FAILED! => {
"changed": false,
"failed": true,
"msg": "unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials. Exception message: (1130, \"Host 'host-10-
}
However, right before that I noticed that:
TASK: [mariadb | Sleeping for 15 seconds while the cluster starts] ************
skipping: [localhost]
This step should have probably not been skipped since the cluster needed actually to be started.
Anyway I worked around the issue in this way:
docker stop mariadb mariadb_data
docker rm mariadb mariadb_data
sudo kolla-ansible deploy
and was able to make progress until the next error ;)