Hi, > On 30 Aug 2019, at 10:31, Mark Goddard <mark at stackhpc.com> wrote: > > On Fri, 30 Aug 2019 at 09:08, Slawek Kaplonski <skaplons at redhat.com> wrote: >> >> Hi, >> >> Recently in Neutron we merged patch [1] which caused error in Kolla-ansible [2]. >> It seems that issue happens on mariadb 10.1 which is used in broken Kolla-ansible job so I started checking what database is used on Neutron’s jobs as we didn’t found any issue with this patch. And it seems that in all scenario/api jobs we have installed mysql 5.7 - see [3] for example. > > Thanks for bringing this up. Just to clarify - mariadb 10.1 is > provided by Ubuntu bionic, so I'd expect others to hit this. In Neutron we are running almost all jobs on Ubuntu Bionic (one is on Fedora and 2 on Centos) and we have Mysql 5.7 installed there instead of Mariadb. > >> >> And the question is - should we maybe switch somehow to Mariadb instead of Mysql? Should it be done globally or maybe it’s only “issue” in Neutron’s CI jobs? >> Or maybe we should have jobs with both Mariadb and Mysql databases? >> >> [1] https://review.opendev.org/#/c/677221 >> [2] https://bugs.launchpad.net/kolla-ansible/+bug/1841907 >> [3] https://2f275f27875ae066d2b6-00a9605a715176e6bd23401c23e881d7.ssl.cf2.rackcdn.com/650846/24/check/tempest-integrated-networking/3fffbd5/controller/logs/dpkg-l.txt.gz >> >> — >> Slawek Kaplonski >> Senior software engineer >> Red Hat >> >> — Slawek Kaplonski Senior software engineer Red Hat