Ask Your Question

# Revision history [back]

### kolla-ansible deploy fails connecting to DB using VIP address!?

Im running the same environment as in: https://ask.openstack.org/en/question/113539/kolla-ansible-ceilometer-bootstrap-failshangs-with-multinode/, but reduced the number of nodes to one each of controller, neutron, compute storage. Still centos7, updated, with ansible 2.5, update pip, and kolla-ansible from PIP.

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Now, if I attach to the containers for mariaDB, there all bound to 172.16.101.100, which is the controller nodes "real" ip address. The only place we're I've added the .111 address, is the globals.yml definition of VIP addresses.

The only use of that address, AFAIK, is for the HA-proxys, to load-share api traffic. So why on earth is it trying to use that address?

I am trying to follow the ansible-yml's, but I cant figure out where it goes wrong, since it seems like such a fundamental error....

### kolla-ansible deploy fails connecting to DB using VIP address!?

Im running the same environment as in: https://ask.openstack.org/en/question/113539/kolla-ansible-ceilometer-bootstrap-failshangs-with-multinode/, but reduced the number of nodes to one each of controller, neutron, compute storage. Still centos7, updated, with ansible 2.5, update updated pip, and kolla-ansible from PIP.PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2)

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Now, Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if I attach to it even should be available after the containers for mariaDB, there all bound to 172.16.101.100, which is the controller nodes "real" ip address. The only place we're I've added the .111 address, is the globals.yml definition of VIP addresses.failed playbook.

The only use weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of that address, AFAIK, is for the HA-proxys, to load-share api traffic. So why on earth is it trying to use that address?control nodes.

So HOW THE HECK can I am trying to follow the ansible-yml's, but I cant figure out where it goes wrong, since it seems like such a fundamental error....troubleshoot this? HELP :'(

### kolla-ansible deploy fails connecting to DB using VIP address!?

Still centos7, updated, with ansible 2.5, updated pip, and kolla-ansible from PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2)

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if it even should be available after the failed playbook.

The weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of the control nodes.

So HOW THE HECK can I troubleshoot this? HELP :'(

### kolla-ansible deploy fails connecting to on DB using VIP address!?connect (which works manually)

Still centos7, updated, with ansible 2.5, updated pip, and kolla-ansible from PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2)

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if it even should be available after the failed playbook.

The weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of the control nodes.

So HOW THE HECK can I troubleshoot this? HELP :'(

### kolla-ansible deploy fails on DB connect (which works manually)

Still centos7, updated, with ansible 2.5, updated pip, and kolla-ansible from PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2)2) Last attempt had 2 nodes of each function. All nodes are always created using qcow-backing images from the same centos-base.

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if it even should be available after the failed playbook.

The weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of the control nodes.

So HOW THE HECK can I troubleshoot this? HELP :'(

### kolla-ansible deploy fails on DB connect (which works manually)

Still centos7, updated, with ansible 2.5, updated pip, and kolla-ansible from PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2) Last attempt had 2 nodes of each function. All nodes are always created using qcow-backing images from the same centos-base.

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if it even should be available after the failed playbook.

The weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of the control nodes.

So HOW THE HECK can I troubleshoot this? HELP :'(

### kolla-ansible deploy fails on DB connect create/connect (which works manually)

Still centos7, updated, with ansible 2.5, updated pip, and kolla-ansible from PIP. I get the same error almost every time, regardless of the number of controller nodes I deploy to(1 or 2) Last attempt had 2 nodes of each function. All nodes are always created using qcow-backing images from the same centos-base.

During deploy, the /neutron/tasks/bootstrap.yml, when trying to create the neutron database, it fails with:

"unable to find /var/lib/ansible/.my.cnf. Exception message: (2003, 'Can\\'t connect to MySQL server on \\'172.16.101.111\\' (110 \"Connection timed out\")')"}


Where ever I look, there is no ".my.cnf" on any host (ctrl, neutron, etc) so should that's ONE problem I dont know how to solve, if it even should be available after the failed playbook.

The weirder problem is that I have NO problems connecting to .111 (the VIP address) if I manually enter "mysql -u haproxy -h <VIP> in either the maradb container, or kolla-toolbox container on either of the control nodes.

So HOW THE HECK can I troubleshoot this? HELP :'(