Ansible 2.0 RC2 is available for testing!

Hi all, we’re happy to announce the second release candidate for Ansible 2.0!

This release candidate includes a few bug fixes and cleanups since rc1 was released, and if we don’t have anything major show up in the next few days we’ll be releasing 2.0-final, so get testing!

For details and background, please see the original beta announcement here: https://groups.google.com/d/msg/ansible-project/_hTjEIpbA_Y/GtllImCkCQAJ

How do you get it?

Thanks for your work!

there is stil this breaking change:

https://github.com/ansible/ansible/issues/13290

and

https://github.com/ansible/ansible-modules-core/issues/2598

https://github.com/ansible/ansible/issues/13375#issuecomment-161379814

“well, in 2.0 missing tags will not error out (yet), but this does seem like an interesting corner case, it should affect empty plays and includes also.”

Hi Jeff, we’re going to let the tags issue slide until a dot release, due to the complexity involved in trying to determine tags from include files. Since includes are now dynamic and can be based on inventory variables (or even variables set during the execution of a playbook), we have no way of knowing for sure which files will be loaded. As a result, any tasks tagged in those files won’t be seen until the file is actually processed. We have some ideas on how to fix this, however we don’t want to hold up the 2.0 release at this time.

It would be nice if this pull request gets in 2.0: https://github.com/ansible/ansible/pull/12909

Only a little change, but very helpfull for people with SLES-11.4 machines :smiley:

Should we flag new 2.0 modules that have bug fixes in PR or recently merged in develop so that they get in to the final 2.0 release version?

It would be nice to not ship new modules with known bugs that already have fixes.

Yes please. Even if they don't make it to 2.0.0 it would be good to
start aseembling a fix of such bugfix PRs to merge for 2.0.1.

-Toshio

Unofficial builds for Fedora and CentOS/RHEL are now available here:
https://copr-fe.cloud.fedoraproject.org/coprs/toshio/ansible-upstream/

-Toshio

s3_bucket region issue - https://github.com/ansible/ansible-modules-extras/pull/1268 it’s already in devel but not rc2
s3_lifecycle issue causing rules to be overwritten [simple fix] - https://github.com/ansible/ansible-modules-extras/pull/1325 - still PR to devel

I commented on both issues but as one is already closed i thought i’d post here too

@rob,

both are now in devel and stable-2.0

Regards
Mirko