kolla-ansible

  1. Bug #1834467
  2. Comment #2

Comment 2 for bug 1834467

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/667904
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=86f373a198620a7082db8e243644fd8d53802c73
Submitter: Zuul
Branch: master

commit 86f373a198620a7082db8e243644fd8d53802c73
Author: Mark Goddard <email address hidden>
Date: Thu Jun 27 12:17:17 2019 +0100

    Fixes for MariaDB bootstrap and recovery

    * Fix wsrep sequence number detection. Log message format is
      'WSREP: Recovered position: <UUID>:<seqno>' but we were picking out
      the UUID rather than the sequence number. This is as good as random.

    * Add become: true to log file reading and removal since
      I4a5ebcedaccb9261dbc958ec67e8077d7980e496 added become: true to the
      'docker cp' command which creates it.

    * Don't run handlers during recovery. If the config files change we
      would end up restarting the cluster twice.

    * Wait for wsrep recovery container completion (don't detach). This
      avoids a potential race between wsrep recovery and the subsequent
      'stop_container'.

    * Finally, we now wait for the bootstrap host to report that it is in
      an OPERATIONAL state. Without this we can see errors where the
      MariaDB cluster is not ready when used by other services.

    Change-Id: Iaf7862be1affab390f811fc485fd0eb6879fd583
    Closes-Bug: #1834467