# Ansible 2.1.1 RC1 is ready for testing **URL:** \ **Category:** Ansible Project\ **Created:** [June 17, 2016, 8:35pm UTC](https://forum.ansible.com/t/ansible-2-1-1-rc1-is-ready-for-testing/21803 "2016-06-17T20:35:22Z")\ **Posts on this page:** 1\ **Page:** 1
**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:** [June 17, 2016, 8:35pm UTC](https://forum.ansible.com/t/ansible-2-1-1-rc1-is-ready-for-testing/21803/1 "2016-06-17T20:35:22Z")
Hi all, we’re happy to announce that RC1 for 2.1.1 is now available for testing. This release candidate fixes many bugs, including (but not limited to): - Fixed some bugs in variable dependency resolution. These were mainly related to includes and roles, to bringe the VariableManager code in-line with our documentation. - Fixed a bug in unarchive, when the destination was a symlinked directory. - Fixed a bug related to performance when loading a large number of groups. - Fixed bugs related to the way host and group vars are loaded, which (for large sets of inventory variables) can reduce CPU and memory usage by 50%. - Fixed a bug where includes were not being implicitly evaluated as static when no loop or variables were being used. - Fixed several more bugs in relation to the way play execution continues or halts when hosts fail, to bringe the behavior more in line with 1.9.x. - Fixed bugs related to the use of the underlying shell executable with the script and raw modules. - Fixed several bugs in relation to the way ssh keys were used with various networking modules. - Fixed a bug related to the way handlers are tracked internally, which could cause bugs when roles are reused within the same play (allow\_duplicates: yes) or when the role dependencies formed a “diamond” pattern. - Fixed a bug related to setfacl on platforms which do not support the -R option for recursive changes. - Many other bug fixes in core/extras modules. How do you get it?