Bug 1508733
Summary: | yum module bug in ansible 2.4.0.0 | ||
---|---|---|---|
Product: | Red Hat Ansible Engine | Reporter: | Chen Li Zhong <lichen> |
Component: | ansible | Assignee: | Pavel Cahyna <pcahyna> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | joerg.kastning, kdreyer |
Target Milestone: | --- | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ansible-2.4.1.0-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-14 10:02:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1509360 | ||
Bug Blocks: |
Description
Chen Li Zhong
2017-11-02 06:15:08 UTC
Note for testing: I was able to reproduce the bug only with packages with a nonzero epoch. # ansible -C -c local -i localhost, -m yum -a 'name=NetworkManager state=latest' localhost localhost | SUCCESS => { "changed": false, "changes": { "installed": [], "updated": [] }, "failed": false, "msg": "", "rc": 0, "results": [ "All packages providing NetworkManager are up to date" ] } (NetworkManager is at version 1:1.8.0-9.el7) but # ansible -C -c local -i localhost, -m yum -a 'name=tzdata state=latest' localhost localhost | SUCCESS => { "changed": true, "changes": { "installed": [], "updated": [ [ "tzdata", "2017c-1.el7.noarch from rhel-7-server-rpms" ] ] }, "failed": false, "msg": "", "rc": 0, "results": [] } (tzdata is at version 0:2017b-1.el7) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3196 |