Ansible 2.0 RC2 is available for testing!

[James Cammarata]

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?

----------------------------------------------------------------------

The tar.gz of the release can be found here:

http://releases.ansible.com/ansible/ansible-2.0.0-0.7.rc2.tar.gz

SHA256: 4f7227260becd444435bc4eddac21c603a725c52eddebff19a2a6708dbbe1462

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git

$ cd ansible

$ git checkout v2.0.0-0.7.rc2

$ git submodule update --init

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be dist/ansible-2.0.0.tar.gz):

$ make sdist

If you discover any errors, or if you see any regressions from playbooks which work on 1.9.x and prior, please open a Github issue and be sure to mention you're testing against this release candidate.

Thanks!

James Cammarata

Director, Ansible Core Engineering

github: jimi-c

[Jeff Reter]

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."

[James Cammarata]

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.

James Cammarata

Director, Ansible Core Engineering

github: jimi-c

--

You received this message because you are subscribed to the Google Groups "Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-deve...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Toshio Kuratomi]

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

-Toshio

[Mirko Friedenhagen]

Regards
Mirko
--
Sent from my mobile

---------- Weitergeleitete Nachricht ----------
Von: "Mirko Friedenhagen" <mfried...@gmail.com>
Datum: 13.12.2015 21:23
Betreff: Re: [ansible-devel] Ansible 2.0 RC2 is available for testing!
An: "James Cammarata" <jcamm...@ansible.com>
Cc:

Hello,

when using 2.0-rc2 I see a difference in Shell locales. While with
1.9.4, an english locale is used, with 2.0 a german locale is used. In
the consequence I get a change in a task like this:

- name: Create diversion for /etc/init.d/{{runit_service}}
  shell: "dpkg-divert --add --divert
/etc/init.d/{{runit_service}},debian /etc/init.d/{{runit_service}}"
  register: diversion_result
  changed_when: "\"Leaving 'local diversion of
/etc/init.d/{{runit_service}} to
/etc/init.d/{{runit_service}},debian'\" not in
diversion_result.stdout"

because the changed_when directive is now getting the german version
of the message.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/