Wait for MariaDB service to be ready through VIP error

Bug #1959969 reported by Maroš Varchola
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
New
Undecided
Unassigned

Bug Description

The problem is, that even if the Mariadb database is fully running, reachable and loggable from ip 192.168.0.200, the haproxy 192.168.0.199 not correctly proxy requests to 192.168.0.200 with this error:

fatal: [localhost]: FAILED! => {"attempts": 6, "changed": false, "cmd": ["docker", "exec", "mariadb", "mysql", "-h", "192.168.0.199", "-P", "3307", "-u", "root", "-pRJQAihupg9j8iVEdD3FstlFt6lAH61Hlwb6ZARSA", "-e", "show databases;"], "delta": "0:00:00.157388", "end": "2022-02-03 23:06:00.035050", "msg": "non-zero return code", "rc": 1, "start": "2022-02-03 23:05:59.877662", "stderr": "ERROR 2013 (HY000): Lost connection to server at 'handshake: reading initial communication packet', system error: 11", "stderr_lines": ["ERROR 2013 (HY000): Lost connection to server at 'handshake: reading initial communication packet', system error: 11"], "stdout": "", "stdout_lines": []}

Inventory is the basic all-in-one with internal and external ips set, internal+external+backend tls enabled too

Thank you for your answers!

kolla-ansible version: 13.1.0
OS: Ubuntu 20.04.3 LTS
Server ip: 192.168.0.200 /24
Server hostname: srv0
domain name 1: sunray.sk
domain name 2: lan

PS: inventory file in the attachments

Revision history for this message
Maroš Varchola (marosvarchola) wrote :
Revision history for this message
Maroš Varchola (marosvarchola) wrote (last edit ):

For better debugging, here is the haproxy mariadb.cfg

path: /etc/kolla/haproxy/services.d/mariadb.cfg

description: updated
description: updated
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.