Damien Ciabrini 1a20780ae0 Remove mariadb-server packages from the host ... During updates/upgrades, installing mariadb-server on the host may impact the behaviour of containerized mysql. During a FFU if mariadb-server is upgraded, it may happen that the rpm scriptlets fail to start mariadb server and leave a crash log behind (tc.log). This prevents the regular online upgrade from happening. During an upgrade, mariadb-server used to be force-upgraded in the mysql service for historical reasons. It's not necessary since mysql is containerized and can trigger the same crash as explained above. During a minor update, the same reasoning can apply if RHEL channel ships a new mariadb-server rpm as scriptlets will probably leave a crash behind as well. Make sure mariadb-server is never installed, while keeping mariadb CLI if already present on the host, to avoid operational impacts. Change-Id: Ib669bb4a5fcbb493d6d5edb5999bd1d87418558b Closes-Bug: #1946742 (cherry picked from commit d33865cded)		2021-10-29 16:34:42 +02:00
..
mysql-base.yaml	Upgrade mariadb storage during upgrade tasks	2021-03-01 13:19:24 +00:00
mysql-client.yaml	Use absolute name to include puppet classes	2020-04-11 08:13:23 +09:00
mysql-container-puppet.yaml	Upgrade mariadb storage during upgrade tasks	2021-03-01 13:19:24 +00:00
mysql-pacemaker-puppet.yaml	Remove mariadb-server packages from the host	2021-10-29 16:34:42 +02:00
redis-base-puppet.yaml	Deprecate service ipv6 params	2020-05-12 07:25:11 +00:00
redis-container-puppet.yaml	Adding key_size option on the certificate creation	2021-01-06 13:18:20 +00:00
redis-pacemaker-puppet.yaml	Use ansible_facts instead	2021-03-01 14:17:11 -07:00