# rolling YUM packages back

**URL:** <https://forum.ansible.com/t/rolling-yum-packages-back/21901>\
**Category:** Ansible Project\
**Created:** [June 30, 2016, 2:31pm UTC](https://forum.ansible.com/t/rolling-yum-packages-back/21901 "2016-06-30T14:31:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dick\_Davies](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@Dick\_Davies](https://forum.ansible.com/u/Dick_Davies)\
**Post date:** [June 30, 2016, 2:31pm UTC](https://forum.ansible.com/t/rolling-yum-packages-back/21901/1 "2016-06-30T14:31:22Z")

</div>

I've got some tasks I use to make sure we're on the correct RPM version.  
Each inventory governs an environment with a common site.yml playbook.

(ansible 1.9.x, centos 6.x)

$environment/group\_vars/all holds vars like

thingy\_rpm: thingy-1.2.3.500

and the play has tasks like

- name: ensure we are on {{ thingy\_rpm }}  
&nbsp;&nbsp;yum: name={{ thingy\_rpm }} state=present  
&nbsp;&nbsp;notify: bounce thingy

This works fine when I'm on a version earlier than 1.2.3.500, but if I need  
to roll back an RPM and try setting

thingy\_rpm: thingy-1.2.2.500

nothing happens.

Am I holding this thing the right way round? Or are the versions in a yum  
task a minimum?

---

<div class="post-metadata">

**Author:** ![jtanner](https://avatars.discourse-cdn.com/v4/letter/j/6bbea6/32.png) [@jtanner](https://forum.ansible.com/u/jtanner)\
**Post date:** [July 1, 2016, 5:00pm UTC](https://forum.ansible.com/t/rolling-yum-packages-back/21901/2 "2016-07-01T17:00:26Z")

</div>

The current module docs for yum state this for the name parameter …

> | Package name, or package specifier with version, like `name-1.0`. When using state=latest, this can be ‘\*’ which means run: yum -y update. You can also pass a url or a local path to a rpm file (using state=present). To operate on several packages this can accept a comma separated list of packages or (as of 2.0) a list of packages.  
>   
> |
> 
> - | - |

Try using the latest version of ansible and see if that resolves the issue. If this is a “downgrade” operation rather than a fresh install, there are open bugs+PRs for that.

```auto
https://github.com/ansible/ansible-modules-core/issues/1419

```

```auto
https://github.com/ansible/ansible-modules-core/pull/2744

```

---

<div class="post-metadata">

**Author:** ![Dick\_Davies](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@Dick\_Davies](https://forum.ansible.com/u/Dick_Davies)\
**Post date:** [July 2, 2016, 8:34pm UTC](https://forum.ansible.com/t/rolling-yum-packages-back/21901/3 "2016-07-02T20:34:13Z")

</div>

Ah thanks - I was using ansible1.9 from an EPEL6 mirror that might not be up to date;  
looks like 1.9.2 or better should sort this out.