Comment out that expire-cache section for now.
This commit is contained in:
parent
abb5fd2041
commit
78ac81e723
1 changed files with 10 additions and 3 deletions
|
@ -10,8 +10,15 @@
|
||||||
user: root
|
user: root
|
||||||
|
|
||||||
tasks:
|
tasks:
|
||||||
- name: expire-caches
|
|
||||||
action: command yum clean expire-cache
|
|
||||||
|
|
||||||
|
# TODO -- I'm not sure if state=latest will go ahead and expire the cache for
|
||||||
|
# us or not. I'll comment this out for now, but if we experience problems in
|
||||||
|
# the future we can just uncomment it. It definitely works with it in place,
|
||||||
|
# the problem is that the expire-cache command is not idempotent which results
|
||||||
|
# in partly confusing ansible-playbook results. -threebean
|
||||||
|
#
|
||||||
|
#- name: expire-caches
|
||||||
|
# action: command yum clean expire-cache
|
||||||
|
#
|
||||||
- name: yum update ${package}
|
- name: yum update ${package}
|
||||||
yum: name=${package} state=latest
|
yum: name=${package} state=latest
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue