2aa7f1ca8a
If the ``use_percona_upstream`` value is changed from True to False, don't remove the existing repository. This is also the source of a bug in Mitaka: We were installing the repo by default and installed the percona-xtrabackup tool with a deb file. If another playbook/role installed percona-xtrabackup, it would override (and probably upgrade) the deb installed version, which is undesired. Change-Id: I2ccc2904d0d4244dc0792411b49763cc3f7e2e22 Closes-Bug: 1653947 Signed-off-by: Jean-Philippe Evrard <jean-philippe.evrard@rackspace.co.uk>
10 lines
346 B
YAML
10 lines
346 B
YAML
---
|
|
fixes:
|
|
- The percona repository stayed in placed even after
|
|
a change of the variable ``use_percona_upstream``.
|
|
From now on, the percona repository will not be
|
|
present unless the deployer decides to
|
|
``use_percona_upstream``. This also fixes a bug
|
|
of the presence of this apt repository after an
|
|
upgdrade from Mitaka.
|