Comment 5 for bug 1692507
Revision history for this message
| Eduardo Gonzalez (egonzalez90) wrote Re: optimize reconfiguration breaks mariadb upgrade | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
Looking into mariadb role changes, seems that optimized reconfiguration breaks mariadb cluster lookup order while upgrading and do a restart of all mariadb containers at the same time causing cluster quorum issues.
TASK [mariadb : include] *******
included: /root/kolla-
TASK [mariadb : Cleaning up temp file on localhost] *******
ok: [192.168.100.244 -> localhost]
TASK [mariadb : Creating temp file on localhost] *******
ok: [192.168.100.244 -> localhost]
TASK [mariadb : Creating mariadb volume] *******
ok: [192.168.100.244]
ok: [192.168.100.186]
TASK [mariadb : Writing hostname of host with existing cluster files to temp file] *******
ok: [192.168.100.244 -> localhost]
ok: [192.168.100.186 -> localhost]
TASK [mariadb : Registering host from temp file] *******
ok: [192.168.100.244]
ok: [192.168.100.186]
TASK [mariadb : Cleaning up temp file on localhost] *******
ok: [192.168.100.244 -> localhost]
TASK [mariadb : include] *******
included: /root/kolla-
TASK [mariadb : Starting mariadb container] *******
changed: [192.168.100.244]
changed: [192.168.100.186]