# Ansible 2.0 RC2 is available for testing!

**URL:** <https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952>\
**Category:** Ansible Project\
**Created:** [December 7, 2015, 6:31pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952 "2015-12-07T18:31:29Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [December 7, 2015, 6:31pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/1 "2015-12-07T18:31:29Z")

</div>

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](https://groups.google.com/d/msg/ansible-project/_hTjEIpbA_Y/GtllImCkCQAJ)

How do you get it?

---

<div class="post-metadata">

**Author:** ![Hauke\_Loffler](https://avatars.discourse-cdn.com/v4/letter/h/b77776/32.png) [@Hauke\_Loffler](https://forum.ansible.com/u/Hauke_Loffler)\
**Post date:** [December 8, 2015, 5:54am UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/2 "2015-12-08T05:54:05Z")

</div>

Thanks for your work!

there is stil this breaking change:

[https://github.com/ansible/ansible/issues/13290](https://github.com/ansible/ansible/issues/13290)

and

[https://github.com/ansible/ansible-modules-core/issues/2598](https://github.com/ansible/ansible-modules-core/issues/2598)

---

<div class="post-metadata">

**Author:** ![Jeff\_Reter](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@Jeff\_Reter](https://forum.ansible.com/u/Jeff_Reter)\
**Post date:** [December 8, 2015, 6:07am UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/3 "2015-12-08T06:07:05Z")

</div>

[https://github.com/ansible/ansible/issues/13375#issuecomment-161379814](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.”

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [December 8, 2015, 2:52pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/4 "2015-12-08T14:52:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Bernhard\_L](https://avatars.discourse-cdn.com/v4/letter/b/7ba0ec/32.png) [@Bernhard\_L](https://forum.ansible.com/u/Bernhard_L)\
**Post date:** [December 8, 2015, 3:09pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/5 "2015-12-08T15:09:34Z")

</div>

> It would be nice if this pull request gets in 2.0: [https://github.com/ansible/ansible/pull/12909](https://github.com/ansible/ansible/pull/12909)

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

---

<div class="post-metadata">

**Author:** ![Rob\_White](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@Rob\_White](https://forum.ansible.com/u/Rob_White)\
**Post date:** [December 9, 2015, 12:34pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/6 "2015-12-09T12:34:36Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [December 9, 2015, 12:54pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/7 "2015-12-09T12:54:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [December 9, 2015, 12:54pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/8 "2015-12-09T12:54:42Z")

</div>

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

-Toshio

---

<div class="post-metadata">

**Author:** ![Rob\_White](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@Rob\_White](https://forum.ansible.com/u/Rob_White)\
**Post date:** [December 10, 2015, 10:14pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/9 "2015-12-10T22:14:37Z")

</div>

s3\_bucket region issue - [https://github.com/ansible/ansible-modules-extras/pull/1268](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](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

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 11, 2015, 3:53pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/10 "2015-12-11T15:53:10Z")

</div>

@rob,

both are now in devel and stable-2.0

---

<div class="post-metadata">

**Author:** ![Mirko\_Friedenhagen](https://avatars.discourse-cdn.com/v4/letter/m/838e76/32.png) [@Mirko\_Friedenhagen](https://forum.ansible.com/u/Mirko_Friedenhagen)\
**Post date:** [December 13, 2015, 8:45pm UTC](https://forum.ansible.com/t/ansible-2-0-rc2-is-available-for-testing/19952/11 "2015-12-13T20:45:30Z")

</div>

Regards  
Mirko
