cleanup: stop setting priority in a follow-up task

We can set priority directly inside the yum_repository module
therefore there's no need for us to actually set it in a follow-up
task that's not idempotent.

Change-Id: Ie5ae5c051055ed532b3ae9dd64c2cb3d15c7173a
This commit is contained in:
Mohammed Naser 2018-12-29 17:56:58 -05:00
parent 8d5ff261dc
commit bca87952a8
1 changed files with 1 additions and 10 deletions

View File

@ -62,6 +62,7 @@
name: "{{ item.name }}"
description: "{{ item.description }}"
baseurl: "{{ item.baseurl }}"
priority: 25
gpgkey: "{{ item.gpgkey | default(omit) }}"
gpgcheck: yes
enabled: yes
@ -73,13 +74,3 @@
- "{{ galera_client_repo }}"
tags:
- galera-repos
# NOTE(hwoarang): MariaDB repository is prioritized at 99 by default
# and that allows yum to install mariadb client from the RDO repos, which
# is not good. This task ensures that the following tasks will choose
# MariaDB repo as the highest priority.
- name: Ensure MariaDB repository takes highest priority
command: |
yum-config-manager
--enable MariaDB
--setopt="MariaDB.priority=25"