MariaDB Bootstrap Container Exits (Non Zero Return Code)

Bug #1607073 reported by Nick
This bug report is a duplicate of:  Bug #1614363: mariadb-bootstrap-failed-script. Edit Remove
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kolla
Incomplete
Undecided
Unassigned

Bug Description

I am running the deploy through a multinode setup onto three servers. When deploying kolla, I get this error message from one of the servers:

TASK [mariadb : Running MariaDB bootstrap container] ***************************
fatal: [192.168.100.60]: FAILED! => {"changed": true, "failed": true, "msg": "Container exited with non-zero return code"}

The deploy continues on the other two servers but fails when waiting for the MariaDB service to be ready:
TASK [mariadb : Waiting for MariaDB service to be ready] ***********************
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (9 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (9 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (8 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (8 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (7 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (7 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (6 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (6 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (5 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (5 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (4 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (4 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (3 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (3 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (2 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (2 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (1 retries left).
FAILED - RETRYING: TASK: mariadb : Waiting for MariaDB service to be ready (1 retries left).
fatal: [192.168.100.61]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_pOF4hV/ansible_module_wait_for.py\", line 537, in <module>\r\n main()\r\n File \"/tmp/ansible_pOF4hV/ansible_module_wait_for.py\", line 478, in main\r\n response = s.recv(1024)\r\nsocket.error: [Errno 104] Connection reset by peer\r\n", "msg": "MODULE FAILURE", "parsed": false}
fatal: [192.168.100.62]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible__H88HJ/ansible_module_wait_for.py\", line 537, in <module>\r\n main()\r\n File \"/tmp/ansible__H88HJ/ansible_module_wait_for.py\", line 478, in main\r\n response = s.recv(1024)\r\nsocket.error: [Errno 104] Connection reset by peer\r\n", "msg": "MODULE FAILURE", "parsed": false}
 to retry, use: --limit @/usr/local/share/kolla/ansible/site.retry

Help?

Changed in kolla:
status: New → Triaged
milestone: none → newton-rc2
Revision history for this message
zhubingbing (zhubingbing) wrote :

please give me more information

Changed in kolla:
importance: Undecided → Critical
status: Triaged → Incomplete
importance: Critical → High
Revision history for this message
Duong Ha-Quang (duonghq) wrote :

(note) Need confirm if it is similar to https://bugs.launchpad.net/kolla/+bug/1614363

Steven Dake (sdake)
Changed in kolla:
importance: High → Critical
status: Incomplete → Triaged
Revision history for this message
zhubingbing (zhubingbing) wrote :

hi,I can't reproduce this bug

type: source base: centos7

1) i run kolla-ansible deploy, no find problme
http://paste.openstack.org/show/582494/

2) kolla-ansible destroy

3) run kollaa-ansible again, maridb work look so good

[root@kolla-master ~]# docker ps -a | grep maria
46e6f5c6de1e 52.196.228.195:4000/kolla/centos-source-mariadb:3.0.0 "kolla_start" 11 minutes ago Up 11 minutes

If the bug exists, can contact me, we work together to replicate the bug
                                                   zhubingbing

Changed in kolla:
status: Triaged → Incomplete
status: Incomplete → Triaged
Changed in kolla:
importance: Critical → Undecided
status: Triaged → Incomplete
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.