Kolla upgrade fail Mariadb keeps on restarting

Bug #1590639 reported by Md Nadeem
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

I have tried to upgrade openstack liberty to Mitaka, however while upgrading Mariadb container goes restarting state and upgrade script get fails. Please find below logs

TASK: [mariadb | Waiting for MariaDB service to be ready] *********************
<localhost> REMOTE_MODULE wait_for port=3306 host=192.168.121.165 search_regex=MariaDB
<localhost> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1465405006.86-12365193347249 && echo $HOME/.ansible/tmp/ansible-tmp-1465405006.86-12365193347249']
<localhost> PUT /tmp/tmp6dHqta TO /root/.ansible/tmp/ansible-tmp-1465405006.86-12365193347249/wait_for
<localhost> EXEC ['/bin/sh', '-c', u'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /root/.ansible/tmp/ansible-tmp-1465405006.86-12365193347249/wait_for; rm -rf /root/.ansible/tmp/ansible-tmp-1465405006.86-12365193347249/ >/dev/null 2>&1']
failed: [localhost] => {"elapsed": 60, "failed": true}
msg: Timeout when waiting for search string MariaDB in 192.168.121.165:3306

FATAL: all hosts have already failed -- aborting

Details logs of Mariadb container is here:

http://pastebin.com/fHUZSyC0

Changed in kolla:
status: New → Triaged
importance: Undecided → High
Changed in kolla:
assignee: nobody → Md Nadeem (mail2nadeem92)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/333753

Changed in kolla:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla (master)

Change abandoned by Md Nadeem (<email address hidden>) on branch: master
Review: https://review.openstack.org/333753
Reason: Need another patch to fix it

Changed in kolla:
assignee: Md Nadeem (mail2nadeem92) → nobody
Changed in kolla:
status: In Progress → Confirmed
Revision history for this message
Derek Yang (hswayne77) wrote :

How did you run the upgrade and what’s the docker version ?

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: High → Undecided
status: Confirmed → Expired
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.