mariadb_recovery playbooks doesn't work as expected

Bug #1769807 reported by Lei Zhang
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Won't Fix
Undecided
Unassigned

Bug Description

My kolla-asible version is queens(6.0.0). In a multi-node deployment, if I stop mariadb container on all nodes, then run "kolla-ansible -i multinode mariadb_recovery", I will get some errors like this:

TASK [mariadb : Registering MariaDB seqno variable] ********************************************************************************************************************************************************
fatal: [controller-1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: list object has no element 0\n\nThe error appears to have been in '/usr/share/kolla-ansible/ansible/roles/mariadb/tasks/recover_cluster.yml': line 54, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Registering MariaDB seqno variable\n ^ here\n"}

line 46 of /usr/share/kolla-ansible/ansible/roles/mariadb/tasks/recover_cluster.yml is

shell: "tail -n 200 /tmp/mariadb_tmp.log | grep Recovered | tail -1 | awk '{print $7}' | awk -F'\n' '{print $1}' | awk -F':' '{print $2}'"

where $7 should be $8, as I checked one of the mariadb.log, it looks like this:
[root@controller-1 mariadb]# cat mariadb.log |grep Recovered | tail -1
2018-05-08 4:11:29 140380250507456 [Note] WSREP: Recovered position: e4f12a6f-5265-11e8-b720-bf1f2e9f6726:9636

If I change $7->$8, then mariadb_recovery run successfully.

Revision history for this message
Radosław Piliszek (yoctozepto) wrote :

Queens is no longer supported.

Changed in kolla-ansible:
status: New → Won't Fix
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.