This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora EPEL. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1404378,1412357 # Description of your update notes=Security fix for CVE-2016-9587 # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
*** Bug 1413581 has been marked as a duplicate of this bug. ***
ansible-2.2.1.0-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cb88734094
ansible-2.2.1.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-418398ce60
ansible-2.2.1.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-418398ce60
ansible-2.2.1.0-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cb88734094
I see builds for Fedora, but is that epel? as this bug was targeted for?
The epel7 build is already stable and has been a while: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-450698b0ed The epel6 build is still in testing: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-dbfb398104 I'm not sure why these bugs got mixed up. :(
one thing I noticed is the above mentioned builds reference CVE-2016-8647 resolved by 2.2.1.0 this is the tracker for CVE-2016-9587 Kurt, not sure but from initial glance it looks like the above mentioned builds comment #8 may cover this bug but are not referenced in the commit messages for the builds.
ansible-2.2.1.0-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
ansible-2.2.1.0-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Jon Schlueter from comment #9) > one thing I noticed is the above mentioned builds reference CVE-2016-8647 > resolved by 2.2.1.0 this is the tracker for CVE-2016-9587 > > Kurt, not sure but from initial glance it looks like the above mentioned > builds comment #8 may cover this bug but are not referenced in the commit > messages for the builds. You'd have to talk to ansible upstream about this.