Skip to content
Snippets Groups Projects
  1. Nov 10, 2021
  2. Nov 09, 2021
  3. Nov 08, 2021
  4. Nov 05, 2021
  5. Nov 04, 2021
  6. Nov 01, 2021
  7. Oct 28, 2021
  8. Oct 27, 2021
  9. Oct 26, 2021
  10. Oct 22, 2021
    • Radosław Piliszek's avatar
      Fix wrong distro assumptions · 4e5e9abc
      Radosław Piliszek authored
      It seems some cases were missed in reviews and not fixed by
      the previous iterations:
      Ifc252ae793e6974356fcdca810b373f362d24ba5
      I838e526b930d5276d3ce24f5188262af7eb33280
      
      Change-Id: Id57da1c5024e1efc5810baca8fbe18967cf95a68
      4e5e9abc
    • Radosław Piliszek's avatar
      Drop enable_host_ntp · 9dee2a92
      Radosław Piliszek authored
      As promised for Xena.
      
      Change-Id: Id634426a1961f0b883068e4ed80e7d1633e5708e
      9dee2a92
  11. Oct 20, 2021
  12. Oct 17, 2021
    • Radosław Piliszek's avatar
      [mariadb] Start new nodes serially · c94cc4a6
      Radosław Piliszek authored
      There seems to be a bug in Galera that causes
      TASK [mariadb : Check MariaDB service WSREP sync status]
      to fail.
      One (in case of 3-node cluster) or more (possible with
      more-than-3-node clusters) nodes may "lose the race" and get stuck
      in the "initialized" state of WSREP.
      This is entirely random as is the case with most race issues.
      MariaDB service restart on that node will fix the situation but
      it's unwieldy.
      The above may happen because Kolla Ansible starts and waits for
      all new nodes at once.
      This did not bother the old galera (galera 3) which figured out
      the ordering for itself and let each node join the cluster properly.
      The proposed workaround is to start and wait for nodes serially.
      
      Change-Id: I449d4c2073d4e3953e9f09725577d2e1c9d563c9
      Closes-Bug: #1947485
      c94cc4a6
  13. Oct 14, 2021
  14. Oct 13, 2021
  15. Oct 12, 2021
  16. Oct 11, 2021
Loading