Ansible v2 upstream rewrite with many bugfixes and new features. See upstream changelog for details: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Ansible v2 with many bugfixes and new features. See upstream changelog for details: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Please log in to add feedback.
This update has been submitted for testing by toshio.
This update has obsoleted ansible-2.0.0.1-1.el7, and has inherited its bugs and notes.
This update has been pushed to testing.
ansible-pull is broken for me - https://github.com/ansible/ansible/issues/13681
this update brakes copying to S3. It always returns 403 NOT AUTHORIZED. Rollbacking to ansible 1.x it works again
Although I'm definitely excited for Ansible 2.0, this is not a backwards-compatible update and is not in line with the update policy. This will break many people's automation and will result in a very poor user experience.
The policy you linked does not apply to EPEL. This policy applies to EPEL
I agree with some of the other downvoters. Ansible 2.0 is great and I thank you for maintaining the package, but please only put 2.0 in Rawhide so that users don't have to port their playbooks except on a major OS upgrade as per the packaging guidelines.
I just tested my ansible 1.9 playbooks on 2.0 and 2.0 is not backwards-compatible.
karma: -1
This is an EPEL update and is possible in EPEL to break things with the updates as explained here. Yes, there is a procedure to do, but this does not mean is not possible. Also here a post in the epel-devel ML has been done
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
Ansible 2.0 is (with a few rare exceptions where it rejects something that 1.9.x permitted, but was incorrect) compatible playbook wise with 1.9.x.
Could everyone here who has hit a playbook that doesn't work with 2.0, but does work with 1.9 file a ticket upstream or a bug report in bugzilla. We want upstream ansible to fix these cases and release 2.0.x with those fixes before we push to stable.
Last week the team I am apart of has been testing our very large (~10K lines) Ansible projects. Most of them have had few issues and a majority of issues were very minor (minutes to resolve). With the added benefits that 2.0 provides I think this package should be updated immediately.
karma: +1
This update has been obsoleted by ansible-2.0.1.0-2.el7.