Hi all, I have a situation where I have to resort to using the shell instead of yum module:
[root@qa-s1-sm1 ansible]# ansible localhost -c local -m yum -a "name=myrpm-db1.5.1 state=latest enablerepo=repo-Snapshots disablerepo=*" localhost | success >> { "changed": false, "msg": "", "rc": 0, "results": [ "All packages providing myrpm-db1.5.1 are up to date" ] } [root@qa-s1-sm1 ansible]# yum --disablerepo=* --enablerepo=repo-Snapshots install myrpm-db1.5.1 Loaded plugins: fastestmirror, keys, presto, s3 Setting up Install Process Loading mirror speeds from cached hostfile repo-Snapshots | 1.5 kB 00:00 Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. --> Running transaction check ---> Package myrpm-db1.5.1.noarch 0:2.5-SNAPSHOT20161010192219 will be updated ---> Package myrpm-db1.5.1.noarch 0:2.5-SNAPSHOT20161107224803 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================== Updating: myrpm-db1.5.1 noarch 2.5-SNAPSHOT20161107224803 repo-Snapshots 138 M Transaction Summary ================================================================================================================================== Upgrade 1 Package(s) rpm -qi myrpm-db1.5.1 Name : myrpm-db1.5.1 Relocations: /usr/local/myapp/pipeline Version : 2.5 Vendor: (none) Release : SNAPSHOT20161010192219 Build Date: Mon 10 Oct 2016 12:36:43 PM PDT Install Date: Tue 11 Oct 2016 11:24:17 AM PDT Build Host: Group : Application Source RPM: myrpm-db1.5.1-2.5-SNAPSHOT20161010192219.src.rpm Size : 162048302 License: 2014 MyComp, Inc. Signature : (none) Packager : pipeline Summary : myrpm-db1.5.1 Description : As you can see from the yum command output, my RPMs also have the Release number incrementally changed and the yum module might not be able to handle this very well. Do you have any recommendations? Or I should file this as a feature request? Thanks. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9908a1f4-a7a0-40c0-9c24-c1a1fb98627b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.