Creating haproxy mysql user

Bug #1644279 reported by wanghongxu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Low
Unassigned

Bug Description

kolla version:4ef26e8(git rev-parse --short HEAD)

[root@controller kolla]# cat /etc/kolla/globals.yml | grep -v "^#" | grep -v "^$"
---
openstack_release: "4.0.0"
kolla_internal_vip_address: "192.168.80.11"
network_interface: "eno16777736"
neutron_external_interface: "eno33554984"

ERROR LOG:

TASK [mariadb : include] *******************************************************
included: /usr/share/kolla/ansible/roles/mariadb/tasks/register.yml for localhost

TASK [mariadb : Creating haproxy mysql user] ***********************************
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (10 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (9 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (8 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (7 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (6 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (5 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (4 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (3 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (2 retries left).
FAILED - RETRYING: TASK: mariadb : Creating haproxy mysql user (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "cmd": ["docker", "exec", "-t", "kolla_toolbox", "/usr/bin/ansible", "localhost", "-m", "mysql_user", "-a", "login_host='192.168.80.136' login_port='3306' login_user='root' login_password='y9t0Q5FXKtTCZQ9hQ5t1LKeqgIOAXWMFB6GODCZj' name='haproxy' password='' host='%' priv=*.*:USAGE"], "delta": "0:00:01.280636", "end": "2016-11-20 19:50:53.532935", "failed": true, "rc": 1, "start": "2016-11-20 19:50:52.252299", "stderr": "", "stdout": "localhost | FAILED! => {\r\n \"changed\": false, \r\n \"failed\": true, \r\n \"msg\": \"unable to connect to database, check login_user and login_password are correct or /home/ansible/.my.cnf has the credentials. Exception message: (1045, \\\"Access denied for user 'root'@'controller' (using password: YES)\\\")\"\r\n}", "stdout_lines": ["localhost | FAILED! => {", " \"changed\": false, ", " \"failed\": true, ", " \"msg\": \"unable to connect to database, check login_user and login_password are correct or /home/ansible/.my.cnf has the credentials. Exception message: (1045, \\\"Access denied for user 'root'@'controller' (using password: YES)\\\")\"", "}"], "warnings": []}
 to retry, use: --limit @/usr/share/kolla/ansible/site.retry

PLAY RECAP *********************************************************************
localhost : ok=62 changed=1 unreachable=0 failed=1

Command failed ansible-playbook -i /usr/share/kolla/ansible/inventory/all-in-one -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=deploy /usr/share/kolla/ansible/site.yml

[root@controller kolla]# docker inspect bootstrap_mariadb | grep -i "password"
                "DB_ROOT_PASSWORD=y9t0Q5FXKtTCZQ9hQ5t1LKeqgIOAXWMFB6GODCZj",

[root@controller ~]# mysql -uroot -h192.168.80.136
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 80
Server version: 10.0.28-MariaDB-wsrep MariaDB Server, wsrep_25.16.rc3fc46e

Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> exit
Bye

description: updated
Changed in kolla:
status: New → Triaged
importance: Undecided → Low
Changed in kolla:
milestone: none → ocata-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

do not see this in the ci and my deployment env. Mark it as incomplete.

Changed in kolla:
milestone: ocata-3 → ocata-rc1
status: Triaged → Incomplete
Mark Goddard (mgoddard)
Changed in kolla:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.