While technically we did install the percona repo for xtrabackup in Mitaka [1], we ensured it's uninstalled [2] before installing the fetched version [3].
I'm not sure there is therefore a regression in Newton/master there: in the container we, by default, use the package, because use_percona_upstream is set to false by default (on ubuntu).
However, if a container was upgraded from M to N, I don't think (I didn't check) the upgrade tool removed this repo, and we don't ensure the repo was removed (that is a bug IMO) [4], so we could end up with a mess.
While technically we did install the percona repo for xtrabackup in Mitaka [1], we ensured it's uninstalled [2] before installing the fetched version [3].
I'm not sure there is therefore a regression in Newton/master there: in the container we, by default, use the package, because use_percona_ upstream is set to false by default (on ubuntu).
However, if a container was upgraded from M to N, I don't think (I didn't check) the upgrade tool removed this repo, and we don't ensure the repo was removed (that is a bug IMO) [4], so we could end up with a mess.
Is that what you encountered?
[1]: https:/ /github. com/openstack/ openstack- ansible- galera_ server/ blob/stable/ mitaka/ tasks/galera_ pre_install. yml#L96
[2]: https:/ /github. com/openstack/ openstack- ansible- galera_ server/ blob/stable/ mitaka/ tasks/galera_ install_ apt.yml# L58-L73
[3]: https:/ /github. com/openstack/ openstack- ansible- galera_ server/ blob/stable/ mitaka/ tasks/galera_ install_ apt.yml# L75-L77
[4]: https:/ /github. com/openstack/ openstack- ansible- galera_ server/ blob/stable/ newton/ tasks/galera_ install_ apt.yml# L92-L99