[ansible-project] Ansible 2.3.4 RC1 is available for testing

[James Cammarata]

​​Hi all, we're happy to announce that rc1 for 2.3.4 is now available for
testing.

This release mainly addresses https://github.com/ansible/ansible/pull/19712,
which was fixed but had not previously been backported to the 2.3.x
releases.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.4.0-0.1.rc1.tar.gz
SHA256: 225774fce740630e15661774598828bd666283258036370e4c9dd8468d1c7fe8

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/
$ cd ansible
$ git checkout v2.3.4-0.1.rc1

You can then source our testing script:

$ . hacking/env-setup

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

$ make sdist

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

--

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua7uFw%2B2eEcPv30_YCkzLdO822TLNZ0_h4ZeE0N%2BMF1WpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.3 has been released

[James Cammarata]

On behalf of the entire Ansible open source community, we are very
happy to announce that Ansible 2.3.3 has been released!

This release includes many bugfixes to the 2.3 codebase.  For full
details, please see the Changelog:

https://github.com/ansible/ansible/blob/stable-2.3/CHANGELOG.md

One CVE is addressed by this release:

* Security fix for CVE-2017-7550 the jenkins_plugin module was logging the
jenkins server password if the url_password was passed via the params
field: https://github.com/ansible/ansible/pull/30875

As always, this update is available via PyPi and
https://releases.ansible.com/ansible/ansible-2.3.3.0.tar.gz
now, and packages for distros will be available as soon as possible.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua6gS%3Dc%2BfXO539T9ogLNBC_AW5haLn%2BYMFpwisXa8OA42Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Why is using args from variables considered unsave?

[James Cammarata]

We consider this unsafe due to the fact that, if the variable is based on a
fact of some kind, your tasks could start doing unexpected or malicious
things (in the event that the remote system is compromised in some way).

In your example, you could still simplify your task by simply restructuring
it a bit:

- file:
src: "{{item.src}}"
dest: "{{item.dest}}"
state: link
  with_items:
  



James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Thu, Mar 16, 2017 at 6:02 AM, Michał Czeraszkiewicz <czer...@gmail.com>
wrote:

> I'm trying out this playbook:
>
> ---
>
> - name: Test
>   hosts: all
>   vars:
> link_list:
>   - src: /etc/hosts
> dest: /tmp/2
> state: link
>   - src: /etc/fstab
> dest: /tmp/1
> state: link
>   - src: /etc/hostname
> dest: /tmp/3
> state: link
>   - src: /etc/resolv.conf
> dest: /tmp/4
> state: link
>   tasks:
> - file:
>   args: "{{ item }}"
>   with_items: "{{ link_list }}"
>
>
>
> I get the following message:
>
> [DEPRECATION WARNING]: Using variables for task params is unsafe,
> especially if the variables come from an external source like facts.
> This feature will be removed in a future release. Deprecation warnings
> can be disabled by setting deprecation_warnings=False in ansible.cfg.
>
> Why is that so?
>
> I think the usage of args is more elegant and feature proof (I don't need
> to extend my role when parameters change in the module) than specifying the
> arguments by hand. See example here
> <https://github.com/geerlingguy/ansible-role-elasticsearch-curator/pull/10/files>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/8de82682-1289-467d-907d-b2b5272045a9%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/8de82682-1289-467d-907d-b2b5272045a9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua7Ja1YcnBRhJ8cQCfhDJttQ_GnZp8KqZtGjiD7GuGcroQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.3 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.3.3 is now available for
testing.

How do you get it?
--

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

https://releases.ansible.com/ansible/ansible-2.3.3.0-0.3.rc3.tar.gz
SHA256: d0dd7b8c913928e78ee938b0da0873368d628fe58089323ee2b0479cd59f7928

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.3.3.0-0.3.rc3

You can then source our testing script:

$ . hacking/env-setup

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

$ make sdist

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

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua5Aom8WcsjLxrzeoEYZLzTVudrARt9EGXZxNMs8FXoJ0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.3 RC1 is available for testing!

[James Cammarata]

Hi all, we're happy to announce that RC1 for 2.3.3 is now available for
testing.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.3.0-0.1.rc1.tar.gz
SHA256: 767bdf018d6d373ea86f80438fe1882b46fb7d9737b4bbdfe27de700c6a33c0b

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.3.3.0-0.1.rc1

You can then source our testing script:

$ . hacking/env-setup

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

$ make sdist

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

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua5St8ysORDeqAmbDXwfMzL3paV%3DhTE-jgLZsXmXWbfUYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 FINAL has been released!

[James Cammarata]

Hi all, we are happy to announce that Ansible 2.3.2 has been released
(sorry for the delay in announcing this, as some of you may have noticed
that we released this on Friday).

The ful list of changes for this release can be found here:

https://github.com/ansible/ansible/blob/v2.3.2.0-1/CHANGELOG.md

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua4kiHx3M11CM5mDkb1zzLiM%2BUvu7RzGkvRQZX3TLb2u7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 RC5 is available for testing

[James Cammarata]

Hi all, we're happy to announce that Ansible 2.3.2 RC5 is available for
testing.

A list of fixes can be found in the CHANGELOG here:

https://github.com/ansible/ansible/blob/v2.3.2.0-0.5.rc5/CHANGELOG.md#bugfixes


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.2.0-0.5.rc5.tar.gz
SHA256: 209bb3a89326c3ac2393e450895a1fa9575226efc47afa094798c8a172c084a7

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua7%2B_3F1FaGpgMEzS6DVQN_NZNwFiRpMn4j1Uc0bdxYk4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 RC4 is available for testing

[James Cammarata]

Hi all, we're happy to announce that Ansible 2.3.2 RC4 is available for
testing.

A list of fixes can be found in the CHANGELOG here:

https://github.com/ansible/ansible/blob/v2.3.2.0-0.4.rc4/CHANGELOG.md#bugfixes


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.2.0-0.4.rc4.tar.gz
SHA256: 1cd21a8cefe8d98c17e794eeae8c34a581d6562eb4416665b418d424e32f6f7a

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAEhzua5m9%2BEUJziN-AF9T01R2K8HmFTMc9qwr_fPXtNnVDf1Ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 RC3 is available for testing

[James Cammarata]

Hi all, we're happy to announce that Ansible 2.3.2 RC3 is available for
testing.

A list of fixes can be found in the CHANGELOG here:

https://github.com/ansible/ansible/blob/v2.3.2.0-0.3.rc3/CHANGELOG.md#bugfixes


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.2.0-0.3.rc3.tar.gz
SHA256: 146dd46d6354ab8a46d38703988c9565221f8150cd244301104e9dd500f01c23

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c
James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFggy%2B%3DscW9E3XJd7EEp00_buZNgq71zA6kGQGa71H1QWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 RC2 is available for testing

[James Cammarata]

Hi all, we're happy to announce that Ansible 2.3.2 RC2 is available for
testing.

Going forward, a list of fixes can be found in the CHANGELOG here:

https://github.com/ansible/ansible/blob/v2.3.2.0-0.2.rc2/CHANGELOG.md#bugfixes


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.2.0-0.2.rc2.tar.gz
SHA256: ea5720187233903b682a154ba05bf41561e741ca803e9fb5792c73e3b278e6eb

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi%3DGmyoYHRLzDXUpdevv_61oZVSe-hp9dSSH2jeHN-9WQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.2 RC1 is available for testing

[James Cammarata]

Hi all, we're happy to announce that Ansible 2.3.2 RC1 is available for
testing.

This release fixes quite a few bugs since the 2.3.1 release, some of which
are:

* Re-enabled non-pipelined mode for winrm/powershell as a work-around for
connection plugins that don't support pipelining.
* Fixed a bug in which facts were not always properly delegated.
* Fixed a bug where child roles were incorrectly included in the dependency
chain when include_role was used.
* Fixed a bug where any_errors_fatal was not properly used when configured
at the play level.
* Fixed a bug where low disk space on the remote system could cause module
execution to fail.
* Directories in /etc/skel will get users ownership when home dir is
created.
* Lots of docker-related module fixes:
  - Fixed #21464 - docker_network: TypeError with existing network.
  - Fixed #22530 - docker_network Failed but Overlay network created
successfully on Docker swarm mode.
  - Properly handle Docker image comparison for published_ports defined as
IP::PORT.
  - Fixed bug where Docker does not output Status after pull anymore.
  - Fixed bug where docker_container with empty links list always restarts.
* Some PY3 bug fixes.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.2.0-0.1.rc1.tar.gz
SHA256: ac01644792a545d65fa3b46b356d1ba8b1ef1589a3a5c7811d1e7dd73cad3833

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgu6QAdRFssTVHb6SALR8%3D2H2mcpdEr0ZJRx%2BWsTrp%2BkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.1 RC2 is available for testing

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.1 RC2!

This release candidate includes a lot of small bug fixes, including (but
not limited to):

* Performance fix when using loops, avoiding default serialization of
classes in dump_attrs.
* Fixed a bug with the copy module, where symlinks were not being properly
followed when doing checksums.
* Fixed a bug where the "always" portion of a block might be incorrectly
skipped.
* Fix to increase the win_async_wrapper fire and forget sleep time.
* Fix pam_limits writing text to a file opened in binary mode.
* Fix template not showing a diff with a directory.
* Fix timeout issue in ansible-connection.
* Fixed a bug related to the new way we manage facts internally.
* Fix for UnboundLocalError while accessing deprecations in result in
module_utils/basic.py.
* Added better detection for dead worker processes in the TQM.
* Fixes for Py3 and winrm connections.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.1.0-0.2.rc2.tar.gz
SHA256: db9aa525739f9a8ee4a8596f35e505afea772c6ed0184ddd601c671ea4a3f511

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiHwOUfG2xiD8ayU%2Be6rCGHASJn-uW0zpW1wg_ea0uSiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.3 FINAL released, 2.1.6rc1 and 2.3.1rc1 avaibale for testing

[James Cammarata]

We are happy to announce that Ansible 2.2.3 FINAL is now available.
Additionally, 2.1.6rc1 and 2.3.1rc1 are also available for testing.

All of these releases address at least one CVE (listed below). Users of
2.2.x should upgrade to 2.2.3 as soon as possible. The CVE impacting 2.1.x
and 2.3.0 is MODERATE in nature, however users should look to upgrade as
soon as the final releases are done.

For the 2.2.3-1 FINAL release:

* [SECURITY] (HIGH): fix for CVE-2017-7466, which was caused by an
incomplete cherry-picking of commits related to CVE-2016-9587.
* [SECURITY] (MODERATE): fix for CVE-2017-7481, in which data for lookup
plugins used as variables was not being correctly marked as "unsafe".
* Fixes a bug when using YAML inventory where hosts were not put in the
'all' group, and some other 'ungrouped' issues in inventory.
* Fixes a bug when using ansible commands without a tty for stdin.
* Split on newlines when searching for become prompt.
* Fix crash upon pass prompt in py3 when using the paramiko connection type.

For 2.3.1 RC1:

* SECURITY (MODERATE): fix for CVE-2017-7481, in which data for lookup
plugins used as variables was not being correctly marked as "unsafe".

For 2.1.6 RC1:

* SECURITY (MODERATE): fix for CVE-2017-7481, in which data for lookup
plugins used as variables was not being correctly marked as "unsafe".


For all of these releases, the fix for CVE-2017-7481 may be a breaking
change. Data returned by lookups is now forced to be unsafe, which means it
will no longer be templated. To allow the old behavior, users have two
options:

1) Add `allow_unsafe=True` to your lookup calls. For example:
`{{lookup('pipe', '/path/to/some/command', allow_unsafe=True)}}`
2) Add `allow_unsafe_lookups=yes` to your ansible.cfg.

*NOTE* Using #2 above will disable all unsafe protections for lookups,
including those used for with_* loops, and is not recommended.


How do you get it?
--

As always, the final release is available via PyPi and releases.ansible.com
now, and packages for distros will be available as soon as possible. The
tar.gz of the release can be found here:

http://releases.ansible.com/ansible/

For the release candidates, you can also test against the git repository as
follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgSjmUiXWFHOwE-hO%2BVW%2BQ8_726NdjMHno9Jh2P1uHn7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 FINAL has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.3.0 has been released!

This release includes many new features and improvements:

* Shared code for modules can now be placed in "module_utils" directories
local to your playbook and/or roles to make it easier to share code across
locally developed modules.
* Allow async tasks to work when an action plugin is used.
* Added a new "dense" callback to produce a more condensed output.
* ~140 new modules, including:
  - A new group of modules to aid in automating your Ansible Tower
instances.
  - A new group of modules for managing oVirt.
  - A few new modules for AWS, including support for KMS and ECS/ECR.

In the network space:

* We’ve introduced new performance upgrades and additional vendor support.
For more information about what’s new with Ansible Networking, take a look
at our blog post (
https://www.ansible.com/blog/networking-features-in-ansible-2-3), and check
out the expanded list of Network Modules now available here:
http://docs.ansible.com/ansible/list_of_network_modules.html.
* This release brings the total number of networking modules up to 267.

For Windows:

* Pipelining support for faster module execution (~20-50% performance boost
for many modules).
* Support for the "runas" become method to execute as a different user and
allow for transparent second-hop authentication in many cases.
* Many other improvements for existing WIndows modules such as check mode,
and other fixes for the winrm connection type.
* Fourteen new modules, including:
  - win_domain
  - win_domain_controller
  - win_domain_membership
  - win_path
  - win_region
  - win_shortcut

Here is the official announcement on our website:

https://www.ansible.com/press/advanced-network-automation-with-2-3

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

Thanks and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgmHHekLEHxZGCZZ69R_33%3DFZhpYW67yyyuMs4AjOdibA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC6 is available for testing!

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC6!

This release is also related to the previous networking fix. After some
further internal discussion, we decided to fix the original problem in a
slightly different way.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.6.rc6.tar.gz
SHA256: a0f923ac6c3b1d79b3fae4ce44ea4d535477782ec6891c58cc9021ca369d4b89

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgWFChue%2BtFOniat%3Dis%2BMCJgdp_ZD%2BEmb2OoXMLqfm_kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC5 is available for testing!

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC5!

A critical bug was found in some of the network modules, so we're releasing
RC5 to address it prior to the final release next week.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.5.rc5.tar.gz
SHA256: 4d208e492b9ba62c5a09c0fb8dd890f888baa1a34e3e4dfdb62c6abe69a5ba3f

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi5zgkgEMmmLB0BQzisMOjX5BB_MoM9%2BgLoV9aP7N6uKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC4 is available for testing!

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC4!

This release candidate fixes a few more last minute bugs, including a lot
of small fixes in networking and windows modules.

* Using "runas" as a become method is marked as "experimental", due to some
caveats.
* Fixed a bug in handler notifications which lead to handlers being run
multiple times in some situations.
* Re-added proxysql modules, which had been added well before the module
cut-off but removed due to some CI issues.

This should hopefully be the last RC before the final 2.3.0 release, so
please be sure to test things out and report any bugs ASAP!

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.4.rc4.tar.gz
SHA256: e5e5e76726a8335aef3ba4b569b80fe2be9614485866056b49abaa82fd5c2d98

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjy4MYRb%2BEXuekXcpLNCRLVkXMq1hBkBmcG6a7TJp8eSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.3 RC1 is available for testing!

[James Cammarata]

We are happy to announce the availability of Ansible 2.2.3 RC1!

This RC addresses a couple of bugs (at least one of which was introduced in
2.2.2):

* Fix 'ungrouped' issue with some inventory formats (#23018)
* Split on newlines when searching for become prompt (also mentioned in
2.3.0 RC3 release)
* Fix crash upon pass prompt in py3 when using the paramiko connection type.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.2.3.0-0.1.rc1.tar.gz
SHA256: 463b809014601612a209096b3ad74f114ea8a6f57804b6efdee142644b254d97

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFg6QV9dZRuDMNgiyus0NcNXKqcmRdhQf1Ycvq7-44sA1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC3 is ready for testing

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC3!

This RC continues to address a few small bugs we wanted to fix before the
final release:

* Fixed a bug in dealing with leading garbage text when looking for a
become prompt.
* Some additional minor correctiosn to network connection plugins.
* Fixed a couple of issues regarding using the synchronize module with
docker connections.
* Several other minor fixes and enhancements.

There will definitely be an RC4 next week, with the final release hopefully
following that.


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.3.rc3.tar.gz
SHA256: 0f06e04c39747efece1452154f82b8d0f3f8639e5eefe74d6b0c6157d8af6d6d

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgPp_EOZ_LANJ8jSPsw_i8-W4YOoWN2bv%2B_ckz722iA3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC2 is available for testing

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC2!

This release candidate includes a lot of small bug fixes, including (but
not limited to):

* Better detection of relative files (DWIM) for roles, fixing some bugs.
* Fix for loosing ungrouped hosts in ini
* Prevent failure for meta: reset_connection
* Synchronize: explicitly set the executable for localhost
* A lot of small fixes for other minor module bugs (especially networking
modules).

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.2.rc2.tar.gz
SHA256: 6a0d909b609d60687a4d22659218517bfc7936d073f43395d8e01dcf2d5e7a30

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFj6Q%3DMXrGw%2BKP8ngn2sqVbNmg%2BOOZJDtpamENb1fc%2Biog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.2 and 2.1.5 FINAL have been released!

[James Cammarata]

Hi all, we are happy to announce that Ansible 2.2.2 and 2.1.5 have been
released.

This release fixes a few bugs introduced in the previous version, as well
as another small tweak to catch an additional way in which CVE-2016-9587
could be triggered.

As always, these updates are available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhtJfgrquhVHdgeKpHG%2BhZ_u-14vwwRgPn6FYB-5p-Urw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.3.0 RC1 is available for testing

[James Cammarata]

(now with a subject...)

We are happy to announce the availability of Ansible 2.3.0 RC1!

There are many new things to try out with this release:

* Shared code for modules can now be placed in "module_utils" directories
local to your playbook and/or roles to make it easier to share code across
locally developed modules.
* Allow async tasks to work when an action plugin is used.
* Added a new "dense" callback to produce a more condensed output.
* A total of 1034 modules (~140 more than 2.2), including:
  - A new group of modules to aid in automating your Ansible Tower
instances.
  - A new group of modules for managing oVirt.
  - A few new modules for AWS, including support for KMS and ECS/ECR.
  - More below...

For Windows:

* Pipelining support for faster module execution (~20-50% performance boost
for many modules).
* Support for the "runas" become method to execute as a different user and
allow for transparent second-hop authentication in many cases.
* Many other improvements for existing WIndows modules such as check mode,
and other fixes for the winrm connection type.
* Fourteen new modules, including:
  - win_domain
  - win_domain_controller
  - win_domain_membership
  - win_path
  - win_region
  - win_shortcut

In the network space:

* We’ve introduced new performance upgrades and additional vendor support.
For more information about what’s new with Ansible Networking, take a look
at our blog post (
https://www.ansible.com/blog/networking-features-in-ansible-2-3), and check
out the expanded list of Network Modules now available here:
http://docs.ansible.com/ansible/list_of_network_modules.html.
* This release brings the total number of networking modules up to 267.

We are tracking a handful of issues for this release candidate that we
expect to have fixed by the time we release version 2.3; you can monitor
the list of known issues here:

https://github.com/ansible/ansible/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20milestone%3A2.3.0

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.1.rc1.tar.gz
SHA256: 0f1f12449e3a981c2f0206ec35cfcccbe8d989b64db1464e53fee30e1e3b2fea

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFh8g4MZo7Ey86dq%3D10HgSyeNtRoRtrkawsxku4w4_mkhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project]

[James Cammarata]

We are happy to announce the availability of Ansible 2.3.0 RC1!

There are many new things to try out with this release:

* Shared code for modules can now be placed in "module_utils" directories
local to your playbook and/or roles to make it easier to share code across
locally developed modules.
* Allow async tasks to work when an action plugin is used.
* Added a new "dense" callback to produce a more condensed output.
* A total of 1034 modules (~140 more than 2.2), including:
  - A new group of modules to aid in automating your Ansible Tower
instances.
  - A new group of modules for managing oVirt.
  - A few new modules for AWS, including support for KMS and ECS/ECR.
  - More below...

For Windows:

* Pipelining support for faster module execution (~20-50% performance boost
for many modules).
* Support for the "runas" become method to execute as a different user and
allow for transparent second-hop authentication in many cases.
* Many other improvements for existing WIndows modules such as check mode,
and other fixes for the winrm connection type.
* Fourteen new modules, including:
  - win_domain
  - win_domain_controller
  - win_domain_membership
  - win_path
  - win_region
  - win_shortcut

In the network space:

* We’ve introduced new performance upgrades and additional vendor support.
For more information about what’s new with Ansible Networking, take a look
at our blog post (
https://www.ansible.com/blog/networking-features-in-ansible-2-3), and check
out the expanded list of Network Modules now available here:
http://docs.ansible.com/ansible/list_of_network_modules.html.
* This release brings the total number of networking modules up to 267.

We are tracking a handful of issues for this release candidate that we
expect to have fixed by the time we release version 2.3; you can monitor
the list of known issues here:

https://github.com/ansible/ansible/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20milestone%3A2.3.0

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.3.0.0-0.1.rc1.tar.gz
SHA256: 0f1f12449e3a981c2f0206ec35cfcccbe8d989b64db1464e53fee30e1e3b2fea

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhYbc7hKtfwCk4A-OugEWaRWaRiQnsyPuLwGVDHPAOzLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.5 and 2.2.2 RC2 are ready for testing

[James Cammarata]

Hi all, we're very happy to announce that RC2 for Ansible 2.1.5 and 2.2.2
are ready for testing!

These rc's include one fix for both 2.2.2 and 2.1.5, and two more fixes
just for 2.2.2:

* Fix azure_rm version checks (#22270) (both 2.2.2 and 2.1.5)
* Fix for traceback when we encounter non-utf8 characters when using --diff
* Ensure ssh hostkey checks respect server port (#20840)

How do you get them?
--

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

http://releases.ansible.com/ansible/ansible-2.1.5.0-0.2.rc2.tar.gz
SHA256: c904f1962c7114675eb252ddb48d2470a3e2363144d62614d5baaa64b58ea047

http://releases.ansible.com/ansible/ansible-2.2.2.0-0.2.rc2.tar.gz
SHA256: 7638af3aaf761e36d42594936d66540e5cba8437a4ac920990af467d99cd3b1b

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFipPAFcsp7t6h-COdBT9FYuyB7VGJJhjYx-5O0f%2B88Rcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Variable precedence change/fix coming in 2.3

[James Cammarata]

Hi all, just wanted to write about a fix/change I'll be merging into the
devel branch soon (ie. as soon as the AWS outage quits impacting our
testing infrastructure), which means it will be included in the 2.3.0
release.

Per our variable precedence docs (
http://docs.ansible.com/ansible/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable),
the variables provided by the inventory script or INI file are supposed to
be lower priority than those found in group_vars and host_vars files,
however this has not been the case in 2.0 and it has gone unnoticed thus
far.

While fixing this to match our documentation however, we realized that the
precedence docs had a problem - variables defined on the host in the
script/INI file would in fact have lower precedence than those in
group_vars/all (or any group_vars files). We've decided to fix this based
on the following rules for inventory:

1) Host Vars > Group Vars
2) Things relative to the playbook > Things relative to the inventory >
Things defined in inventory

For those who are unfamiliar with the second point above, it is possible to
have host/group vars files defined relative to both the playbook and to the
inventory. For example, if you have:

playbook/site.yml
playbook/group_vars/all
inventory/hosts
inventory/group_vars/all

And you run:

$ ansible-playbook -i inventory/hosts playbook/site.yml

the variables in playbook/group_vars/all will "win" over those in
inventory/group_vars/all.

Prior to this change, if you had something like:

ansible_connection: local

In any group_vars/all file, it would have "won" over anything defined in
the inventory script, even if you did something like:

myhost ansible_connection=paramiko

the value in the group_vars would have been the value used, which is
counter-intuitive.

If anyone has any questions regarding this change, please let us know.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgMtr%2B4dYEpZ%2BqCjPXfRf%3DEDdK%3DN3L1RubgRZORJfTbvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.5 and 2.2.2 RC1 are ready for testing

[James Cammarata]

Hi all, we're very happy to announce that RC1 for Ansible 2.1.5 and 2.2.2
are ready for testing!

First and foremost, these release candidates address two security issues:

* [SECURITY] (HIGH) handle some additional corner cases in the way
conditionals are parsed and evaluated (both 2.1.5 and 2.2.2)
* [SECURITY] (LOW) properly filter passwords out of URLs when displaying
output from some modules (both 2.1.5 and 2.2.2)

The first of these is a continuation of the bug fixes related to
CVE-2016-9587.

Other bug fix highlights:

* Use proper PyYAML classes for safe loading YAML files (both 2.1.5 and
2.2.2)
* Fix for bug related to when statements for older jinja2 versions (both
2.1.5 and 2.2.2)
* Fix a bug/traceback when using to_yaml/to_nice_yaml (both 2.1.5 and 2.2.2)
* Properly clean data of jinja2-like syntax, even if that data came from an
unsafe source (both 2.1.5 and 2.2.2)
* Fix bug regarding undefined entries in HostVars
* Skip fact gathering if the entire play was included via conditional which
evaluates to False
* Fixed a performance regression when using a large number of items in a
with loop
* Fixed a bug in the way the end of role was detected, which in some cases
could cause a role to be run more than once
* Add jinja2 groupby filter override to cast namedtuple to tuple to handle
a non-compatible change in jinja2 2.9.4-2.9.5
* Fixed several bugs related to temp directory creation on remote systems
when using shell expansions and become privilege escalation
* Fixed a bug related to spliting/parsing the output of a become privilege
escalation when looking for a password prompt
* Several unicode/bytes fixes

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.5.0-0.1.rc1.tar.gz
SHA256: 194e0ed0dde7e48de183026cc9e46a6886f1591a4a8da6bce705d70143a6a9b5

http://releases.ansible.com/ansible/ansible-2.2.2.0-0.1.rc1.tar.gz
SHA256: 8b9035ff99323dd9df43a9f4c789ffcc5913ced1ef5c829a8dd35cafe0e62846

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout 
$ 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 in the dist/ directory):

$ 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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjif91%2Bn8tCT-LnGLC8Oa3PFgbuJyByMizSqbTqZ4E%3DzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.1 and 2.1.4 FINAL have been released!

[James Cammarata]

Hi all, we are happy to announce that Ansible 2.2.1 and 2.1.4 have been
released.

This release fixes a few bugs, but the main fix is for CVE-2016-9587 which
was previously disclosed during the RC process.

As always, these updates are available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjrNuSO8dUWy2uA2LhKTVPr1ohAOuhSLJOPo%3DLStYNdRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] IMPORTANT - Updated (x2) RCs for Security Bug CVE-2016-9587

[James Cammarata]

Hi all,

We are releasing a new set of candidates for the security bug in
CVE-2016-9587:

2.1.4 RC3
2.2.1 RC5

Due to this release, we are moving the final release to Monday, January
16th. Sorry for the delay in getting the finals out.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhp3y2HK7hTT3WgnGhUh6c%2BfysX9F-aJzsg2%3DC%2BwhyeSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] IMPORTANT - Updated RCs for Security Bug CVE-2016-9587

[James Cammarata]

Hi all,

We've just released the following release candidates to address a few more
corner cases found after the release of the previous RCs for CVE-2016-9587:

2.1.4 RC2
2.2.1 RC4

Thanks again to Computest for double-checking our fixes and pointing out a
couple of places we had missed.

We are still looking to get the final releases out by the end of the week,
so please be sure to test these RC's for any breaks in your playbooks.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhr9YATUE_O012avTRxE_Wtz%3Diw2H-i0Vkv46Zx9ZXaOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] IMPORTANT - New RCs for Security Bug CVE-2016-9587

[James Cammarata]

Hi all,

Today we are releasing two new release candidates to address CVE-2016-9587,
which we are removing from embargo today:

2.1.4 RC1
2.2.1 RC3

CVE-2016-9587 is rated as HIGH in risk, as a compromised remote system
being managed
via Ansible can lead to commands being run on the Ansible controller (as
the user
running the ansible or ansible-playbook command).

If you have the ability, please test the above release candidates so that
we can get
the final releases out as quickly as possible.

Finally, thanks to the security team at Computest, who did an amazing job
of finding
the flaws and creating an excellent set of tests to reproduce them for us.

Thanks, and let us know if you run into any problems with the above release
candidates!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgYBK-Ze4YE5ocxfRVobRCV_WDRmbf8Cj3_dxMMMGJNpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.1 RC2 is ready for testing

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.2.1 RC2 is ready for
testing!

Some bug fix highlights:

* Fixed a bug in the path searching/resolution for jinja2 includes in
template files.
* Fixed a bug where include_role resulted in tasks which were not properly
inheriting variables from a parent role.
* Fixed a bug related to using scp instead of sftp when using the ssh
connection plugin.
* Fixed a bug related to setfacl on Solaris and other OS versions which use
strict POSIX ACLs.
* Fixed a bug in the AnsiBallz (zip) support for modules where the system
clock on the remote system was incorrect (and pre-1980).
* Fix for bugs in the mount module.
* Fixed a bug in the "atomic_move" which could result in a traceback.
* Fix for a bug in the way conditionals evaluate "is defined" and "is
undefined" and other logical variants.
* Fix for a bug related to the way iterating over HostVars works.
* Some fixes for unicode issues in paths and other places.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.2.1.0-0.2.rc2.tar.gz
SHA256: 8421839958ab9b8f0f9ddcce02ed4bc680be89ae6d9a8b3059bdd99577b873c0

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.2.1.0-0.2.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.2.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhuc8yJX7UV%3Dohcte7Kex7SBppKaLuAm9kZh9ywVh%2BhRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] IMPORTANT - Ansible Repository Merge

[James Cammarata]

Hi all, just wanted to announce/remind people about the upcoming repo merge.

The Plan:
-

Next week, we'll be re-merging the module repositories back into
ansible/ansible on GitHub. The two module repos will be essentially locked,
though they will be kept in place for the existing 2.1 and 2.2
dependencies. Once 2.2 moves out of official support (in about a year),
we'll completely remove those repositories. Until then, any issues/PRs
opened there will be auto-closed with a note to open it on ansible/ansible.

Why Are We Doing This (Again...)?
-

For those who've been using Ansible long enough, you know that originally
we started with a single repository. The original intention of the core vs.
extras split was that core would be better supported/tested/etc. Extras
would have been a bit more of a "wild-west" for modules, to allow new
modules to make it into the distribution more quickly. Unfortunately this
never really worked out, as well as the following:

1. Many modules in the core repo were also essentially "grand-fathered" in,
despite not having a good set of tests or dedicated maintainers from the
community.
2. The time in queue for modules to be merged into extras was not really
any different from the time to merge modules into core.
3. The split introduced a few other problems for contributors such as
having to submit multiple related PRs for modules with tests, or for those
which rely on action plugins.
4. git submodules are notoriously complicated, even for contributors with
decent git experience. The constant need to update git submodule pointers
for devel and each stable branch can lead to testing surprises and really
buys us nothing in terms of flexibility.
5. Users can already be confused about where to open issues, especially
when the problem appears to be with a module but is actually an action
plugin (ie. template) or something more fundamental like includes. Having
everything back in one repo makes it easier to link issues, and you're
always sure to open a bug report in the right place.

Issues and PRs:
-

We're working on creating a tool which will allow users to migrate their
issues from ansible-modules-core and ansible-modules-extras, details of
that will be available next week as well. PRs will be a bit more tricky,
though we are working on a script/process to make it easier for users to
move their PRs from the existing repos into the ansible/ansible code base
post-merge, however in most cases PRs will need to be resubmitted or left
in the respective module repository until we can revisit them ourselves.

Metadata - Support/Ownership and Module Status:
--

As part of this move, we will be introducing module metadata, which will
contain a couple of pieces of information regarding modules:

1. Support Status: This field indicates who supports the module, whether
it's the core team, the community, the person who wrote it, or if it is an
abandoned module which is not receiving regular updates. The Ansible team
has gone through the list of modules and we have marked about 100 of them
as "Core Supported", meaning a member of the Ansible core team should be
actively fixing bugs on those modules. The vast majority of the rest will
be community supported. This is not really a change from the status quo,
this just makes it clearer.
2. Module Status: This field indicates how well supported that module may
be. This generally applies to the maturity of  the module code however, not
necessarily its bug status.

The documentation pages for modules will be updated to reflect the above
information as well, so that users can evaluate the status of a module
before committing to using it in playbooks and roles.

Summary:
-

For the vast majority of Ansible end-users, we expect this change to have
little impact. The impact on developers will definitely be higher, though
we're really trying to make it much smoother than when we made the original
split.

If you have any questions or concerns regarding this, please be sure to let
us know ASAP.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFh%2BpzAQeCYXM%2BCOJBCX1jcUGT7GuYtsX0s5GnA2fwmmcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.1 RC1 is ready for testing

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.2.1 RC1 is ready for
testing!

Some bug fix highlights:

* Fixes a bug where undefined variables in with_* loops would cause a task
failure even if the when condition would cause the task to be skipped.
* Fixes multiple bugs related to field/attribute inheritance in nested
blocks and includes, as well as task iteration logic during failures.
* Fixes a bug with "vault rekey" when using environment variables to
specify the vault password file.
* Fixes a bug in which include_vars was not working with failed_when.
* Fixes several bugs related to properly incrementing the failed count in
the host statistics.
* Fixes a bug with listening handlers which did not specify a `name` field.
* Fixes a bug with the `play_hosts` internal variable, so that it properly
reflects the current list of hosts.
* Fixes a bug related to the v2_playbook_on_start callback method and
legacy (v1) plugins.
* Fixes an openssh related process exit race condition, related to the fact
that connections using ControlPersist do not close stderr.
* Improvements and fixes to OpenBSD fact gathering.
* More python 3 fixes.

Modules:

* Fixes a bug where the pip module was not properly installing things/using
the wrong pip executable when run from inside a venv.
* Fixes for the service/systemd module.
* Fixes for several packaging modules, including apt, yum and dnf.
* Several fixes for bugs in the cron module.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.2.1.0-0.1.rc1.tar.gz
SHA256: ab291167fba14c0ae0cae4c30671dd0acf097ecf99128daea0f4831b5bc748e1

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.2.1.0-0.1.rc1
$ 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.2.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjq7oMta9PB0KSrhpY9AWUw7tSCiU_KEOQzowOsnDP8JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.3 FINAL has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.1.3 has been released!

This release fixes many bugs, including the two CVE-related bugs also fixed
in the 2.2.0 release:

* Security fix for CVE-2016-8628 - Command injection by compromised server
via fact variables. In some situations, facts returned by modules could
overwrite connection-based facts or some other special variables, leading
to injected commands running on the Ansible controller as the user running
Ansible (or via escalated permissions).
* Security fix for CVE-2016-8614 - apt_key module not properly validating
keys in some situations.
* Fixed several bugs related to locating files relative to role/playbook
directories.
* Fixed a bug in the way hosts were tested for failed states, resulting in
incorrectly skipped block sessions.
* Fixed a bug in the way our custom JSON encoder is used for the to_json*
filters.
* Fixed some bugs related to the use of non-ascii characters in become
passwords.
* Fixed postgres* and subversion modules to ensure password fields were not
displayed when no_log=True is used.
* Fixed a bug with Azure modules which may be using the latest rc6 library.
* Backported some docker_common fixes.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible. We have
also created the following PPA for 2.1.x versions:

https://launchpad.net/~ansible/+archive/ubuntu/ansible-2.1

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiGAiMJVNh2jadQOCkFua4CbL%3Duxw7kH0QmRgv2PzFv2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Ansible 2.2.0 Final has been released!

[James Cammarata]

Hi Igor,

While 2.2 is quite a bit faster than 2.0/2.1, it does still lag a bit
behind 1.9. Mainly this slowness is due to the way we've changed how
workers are created, which in 2.0+ allows us to have strategies but does
come with a hit to performance. We'll still look at ways of improving
things in the future, so any analysis/debugging of performance problems is
always appreciated.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Tue, Nov 1, 2016 at 7:08 PM, Igor Cicimov <ig...@encompasscorporation.com
> wrote:

> Hi James,
>
> Although the performance improvements are welcomed, I wonder how does this
> stack compared to 1.9.x version?
>
> There have been discussions here, more specific https://groups.google.com/
> forum/#!starred/ansible-devel/UU0Tpw-qlhY, and couple of issues raised
> and outlined in your post here https://groups.google.com/
> forum/#!starred/ansible-devel/TLEc1NoQ7lA, that revel a serious problem
> in the very core of 2.x release. Has this been addressed in 2.2.0 and if
> yes how close is the 2.2 performance to the old 1.9.x branch?
>
> Thanks,
> Igor
>
>
> On Wednesday, November 2, 2016 at 12:55:28 AM UTC+11, James Cammarata
> wrote:
>>
>> Hi all, we're very happy to announce that Ansible 2.2.0 has been released!
>>
>> This release includes many new features and improvements (from the RC1
>> release announcement):
>>
>> * Almost 200 new modules!
>> * Major performance improvements. In many cases, you should see a 2-3x
>> improvement over 2.1/2.0.
>> * `include_role` now allows for roles to be executed inline with your
>> other tasks, instead of listing them only in the `roles:` section of your
>> plays (http://docs.ansible.com/ansible/include_role_module.html)
>> * The `listen` feature for handlers allows for much easier notifications
>> of multiple handlers via a pub/sub mechanism (
>> http://docs.ansible.com/ansible/playbooks_intro.html#handle
>> rs-running-operations-on-change).
>> * Serial batches can now be specified as a list rather than a single
>> integer value, meaning you can do something like this to scale up serial
>> batches:
>>   `serial: [1, 5, 10]` # the first batch will be 1 host, 2nd=5 hosts, all
>> other batches will be 10 hosts)
>> * Windows tasks can now use "async", and can also now use the
>> "environment" option to set environment variables.
>> * Support for binary modules.
>> * New become method: `ksu` (Kerberos su).
>> * New meta option: `end_play`, which allows for early termination of a
>> play without failing.
>> * Meta tasks now support conditional statements.
>>
>> Here is the official announcement on our website:
>>
>> https://www.ansible.com/press/ansible-22-delivers-new-automa
>> tion-capabilities-for-containers-networks-and-cloud
>>
>> As always, this update is available via PyPi and releases.ansible.com
>> now, and packages for distros will be available as soon as possible.
>>
>> Thanks and enjoy!
>>
>> James Cammarata
>>
>> Ansible Lead/Sr. Principal Software Engineer
>> Ansible by Red Hat
>> twitter: @thejimic, github: jimi-c
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/ee7e7988-436a-4e6f-a13f-fcdb2f8d4301%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/ee7e7988-436a-4e6f-a13f-fcdb2f8d4301%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiuyWq9Ttwgssnz3HF95RmwrTj5iTBbsXNQvmzDAbXTbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.2 behaviour on includes.

[James Cammarata]

Hi Harold, was this working on 2.1?

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Tue, Nov 1, 2016 at 6:10 PM, <ansible.use...@gmail.com> wrote:

> Hi,
>
> I have one script which includes another and now with ansible 2.2 it
> generates a fatal error:
>
> script 1: t.yml
> ---
> - hosts: localhost
>   connection: local
>   gather_facts: no
>
>   tasks:
>
> - set_fact: check_number="0"
> - include: y.yml
>   when: check_number == "1"
>
> script 2: y.yml
>
> ---
> - set_fact: mymsg="Does this work"
> - shell: echo "{{ item }}"
>   with_items:
> - "{{ mymsg }}"
>
> If I execute the script in ansible 2.2 it fails
>
> $ ansible-playbook t.yml
>
> PLAY [localhost] **
> *
>
> TASK [set_fact] **
> **
> ok: [localhost]
>
> TASK [set_fact] **
> **
> skipping: [localhost]
>
> TASK [command] **
> ***
> fatal: [localhost]: FAILED! => {"failed": true, "msg": "'mymsg' is
> undefined"}
> to retry, use: --limit @/devops/provision/ansible/t.retry
>
> PLAY RECAP 
> *
> localhost  : ok=1changed=0unreachable=0failed=1
>
> It always ran with previous version although with a error message
>
> $ ansible-playbook t.yml
> statically included: /Users/hrf/jelli/devops/provision/ansible/y.yml
>
> PLAY [localhost] **
> *
>
> TASK [set_fact] **
> **
> ok: [localhost]
>
> TASK [set_fact] **
> **
> skipping: [localhost]
>
> TASK [command] **
> ***
> [DEPRECATION WARNING]: Skipping task due to undefined Error, in the future
> this will be a fatal error.: 'mymsg' is undefined.
> This feature will be removed in a future release.
> Deprecation warnings can be disabled by setting deprecation_warnings=False
> in ansible.cfg.
> skipping: [localhost]
>
> PLAY RECAP 
> *
> localhost  : ok=1changed=0unreachable=0failed=0
>
> This was done before blocks were available.  It was my way of executing a
> block of code on a conditional basis.  It seems reasonable that this should
> work even with ansible 2.2 without being a fatal error.
>
> Thanks,
> -Harold
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/b2476212-0068-46c7-9e67-b321db51d94c%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/b2476212-0068-46c7-9e67-b321db51d94c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFj9wAi%3DCmsrLOWPD-0kGuY1HCFZLd5kjnhWVtKpfCCk1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.0 Final has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.2.0 has been released!

This release includes many new features and improvements (from the RC1
release announcement):

* Almost 200 new modules!
* Major performance improvements. In many cases, you should see a 2-3x
improvement over 2.1/2.0.
* `include_role` now allows for roles to be executed inline with your other
tasks, instead of listing them only in the `roles:` section of your plays (
http://docs.ansible.com/ansible/include_role_module.html)
* The `listen` feature for handlers allows for much easier notifications of
multiple handlers via a pub/sub mechanism (
http://docs.ansible.com/ansible/playbooks_intro.html#handlers-running-operations-on-change
).
* Serial batches can now be specified as a list rather than a single
integer value, meaning you can do something like this to scale up serial
batches:
  `serial: [1, 5, 10]` # the first batch will be 1 host, 2nd=5 hosts, all
other batches will be 10 hosts)
* Windows tasks can now use "async", and can also now use the "environment"
option to set environment variables.
* Support for binary modules.
* New become method: `ksu` (Kerberos su).
* New meta option: `end_play`, which allows for early termination of a play
without failing.
* Meta tasks now support conditional statements.

Here is the official announcement on our website:

https://www.ansible.com/press/ansible-22-delivers-new-automation-capabilities-for-containers-networks-and-cloud

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

Thanks and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFg7-pHVf-BZPmCNp6wbMhBptPKG%3DXOe3%3DoFc9MPCu%3DtTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.3 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.1.3 is now available for
testing.

This release candidate addresses the following bugs:

* Fixed a bug where a custom module could overwrite connection-based
variables.
* Fixed a bug with apt_key, where the use of long keys caused some problems
(#5237, #5353, #5357)
* Fixed a bug with Azure modules which may be using the latest rc6 library.
* Backported some docker_common fixes.

For those who may have noticed, we skipped an official RC2 announcement as
we decided to include a few additional fixes after RC2 had been tagged and
uploaded, so testers should use this most recent RC3.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.3.0-0.3.rc3.tar.gz
SHA256: 4517b38a261b975f59baef3d7b522f9b84042a39ad24638983d4b0705597f3f4

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.3.0-0.3.rc3
$ 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.1.3.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiFpAoUhew56dHq7N60XHHnyrQD%2Bd3aL_zqJT2o%3DggdPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.2.0 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.2.0 is now available for
testing.

This release candidate addresses the following bugs:

* Fixed a bug where a custom module could overwrite connection-based
variables.
* Fixed a bug with apt_key, where the use of long keys caused some problems
(#5237, #5353, #5357)
* Fixed a race condition bug in the new Windows async support.
* Fixed a bug where include_role was not failing if the specified
"tasks_from" file was not found.
* Fixed a bug related to async tasks running in check mode.
* Fixed a bug with handlers so that both by name and by listen target work.
* Fixed a bug related to 'smart' connection mode and the scp_if_ssh setting
when fetching files.
* Various fixes related to facts.
* Many more Python 3 fixes.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.2.0.0-0.3.rc3.tar.gz
SHA256: 9bd7443428dee83b8c6344c2730bf4c640589e0f24b8671c1de2b0c5d831facb

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.2.0.0-0.3.rc3
$ 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.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjWixyxW96ZjvTuM_jT1fW2LwYPDR7dtRBwg5AxhF1V-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.3 RC1 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC1 for 2.1.3 is now available for
testing.

This release candidate addresses the following bugs:

* Fixed several bugs related to locating files relative to role/playbook
directories.
* Fixed a bug in the way hosts were tested for failed states, resulting in
incorrectly skipped block sessions.
* Fixed a bug in the way our custom JSON encoder is used for the to_json*
filters.
* Fixed some bugs related to the use of non-ascii characters in become
passwords.
* Fixed postgres* and subversion modules to ensure password fields were not
displayed when no_log=True is used.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.3.0-0.1.rc1.tar.gz
SHA256: 20ba6fa21632a96c6727edd080a4184e91c0aa756391d7a88988e626de66d961

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.3.0-0.1.rc1
$ 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.1.3.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhVMj88DECcxDFpzg6775zSM%2B212Xxy25Rhi2a8yhM3Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 FINAL has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.1.2 has been released!

This release fixes many bugs, which can be found in the CHANGELOG or the
previous RC-related emails for 2.1.2.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjVKCKxA%2Bprb-Rp-OcAUNdCsKS49xfEe2ZFN8JNMWt2kg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 RC5 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC5 for 2.1.2 is now available for
testing.

This release candidate fixes a bug introduced in the mount module in RC4.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.5.rc5.tar.gz
SHA256: 7e3cb826d9a115e540646c2436e2c19625ab057b2950560d93c0db915649282e

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.5.rc5
$ 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.1.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjSajrg5JO5Vwe7L_F7%3D%3DVz7a%3DnXbTvU21s2rNLNxThWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Ansible 2.1.2 RC4 is ready for testing

[James Cammarata]

Good catch Jesse, we're looking into it and we'll cut RC5 asap.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Tue, Sep 27, 2016 at 1:28 AM, Jesse Pretorius <jesse.pretor...@gmail.com>
wrote:

> On Monday, 26 September 2016 20:57:14 UTC+1, James Cammarata wrote:
>>
>> Hi all, we're happy to announce that RC4 for 2.1.2 is now available for
>> testing.
>>
>
> Unfortunately I get a pretty quick fail:
>
> http://logs.openstack.org/65/351165/25/check/gate-
> openstack-ansible-openstack-ansible-aio-ubuntu-trusty/
> 8758449/console.html#_2016-09-27_05_57_48_061918
>
> When executing:
>
> https://github.com/openstack/openstack-ansible/blob/master/
> tests/roles/bootstrap-host/tasks/prepare_data_disk.yml#L63-L73
>
>
>
> --
> 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-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgtdqczW3WbL8HVKc1W3WAkOarvj2qDf9cpAMxCay930g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 RC4 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC4 for 2.1.2 is now available for
testing.

This release candidate also adds the following fixes for bugs:

* Fixed a bug related to creation of retry files (#17456)
* Fixed a bug in the way include params are used when an include task is
dynamic (#17064)
* Fixed a bug related to including blocks in an include task (#15963)
* Fixed a bug related to the use of hostvars internally when creating the
connection plugin. This prevents things like variables using lookups from
being evaluated unnecessarily (#17024)
* Fixed a bug where using a variable containing a list for the `hosts` of a
play resulted in an list of lists (#16583)
* Fixed a bug where integer values would cause an error if a module param
was of type `float` (no issue)
* Fixed a bug with net_template failing if src was not specified (#17726)

Module fixes:
* ini_file:
  - Fixed a bug where option lines are now inserted before blank lines.
  - Fixed a bug where leading whitespace prevented matches on options.
* Fixed a bug in iam_cert when dup_ok is used as a string.
* Fixed a bug in postgresql_db related to the changed logic when
state=absent.
* Fixed a bug where single_transaction and quick were not passed into
db_dump for the mysql_db module.
* Fixed several bugs with mount.
* Fixed several more minor bugs in extras modules.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.4.rc4.tar.gz
SHA256: 2e2a10090cdd50ea0970e4368949d8c3b75d1d62618fab738c475adb6c1d8e87

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.4.rc4
$ 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.1.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFh%3DQLR4y3cVDmzgytVx5aRa4XbdQFHp3MvQK_qptznu7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.1.2 RC3 is ready for testing

[James Cammarata]

I don't believe that's fixed in devel yet, so no it won't be in 2.1.2.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Wed, Sep 21, 2016 at 2:49 PM, nusenu <nus...@openmailbox.org> wrote:

>
>
> James Cammarata:
> > Hi all, we're happy to announce that RC3 for 2.1.2 is now available for
> > testing.
> >
> > This release candidate also adds the following fixes for bugs:
> [...]
>
> Looks like a fix for regression
> https://github.com/ansible/ansible/issues/14829
> is not included yet. Will it be fixed in final 2.1.2?
>
> thanks,
> nusenu
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/f5f654f6-2338-b7b1-c192-
> 11b7d8852d84%40openmailbox.org.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFg84GG-ha-qTwzzU%2BQevSp%2Bu3GjGC3eQqdfESBLMqrDTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.1.2 is now available for
testing.

This release candidate also adds the following fixes for bugs:

* Backported a fix for a bug in the _fixup_perms module helper code (#17427)
* Fixed a bug in "ansible-galaxy import" (#17417)
* Fixed a bug where the temporary CA files created by the module helper
code were not being deleted properly in some situations (#17073)
* Fixed many bugs in the unarchive module
* Fixes for module ec2:
  - Fixed a bug related to source_dest_check when used with non-vpc
instances (core#3243)
  - Fixed a bug in ec2 where instances were not powering of when referenced
via tags only (core#4765)
  - Fixed a bug where instances with multiple interfaces were not powering
up/down correctly (core#3234)
* Fixes for module get_url:
  - Fixed a bug in get_url module to force a download if there is a
checksum mismatch regardless of the last modified time (core#4262)
  - Fixed a bug in get_url module to properly process FTP results
(core#3661 and core#4601)
* Fixed a bug in win_user related to users with disabled accounts/expired
passwords (core#4369)
* Several minor fixes in extras modules

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.3.rc3.tar.gz
SHA256: 967b4688b4e0ccd7dcd120c6dbbed2da45fabf2fde2798a4a16d340e0e355336

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.3.rc3
$ 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.1.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjM_gOiQJnhZ1gmEUnEmPnEmQR99-5%2BfOhhxqW4GKU5FQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Ansible 2.1.2 RC2 is ready for testing

[James Cammarata]

Hi John,

Our roadmaps have been posted here since 2.1:
https://github.com/ansible/ansible/blob/devel/ROADMAP.rst

Was there something else to which you were referring?

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Thu, Sep 8, 2016 at 1:43 PM, <jpeac...@sparkpost.com> wrote:

>
>
> On Wednesday, August 31, 2016 at 2:25:23 PM UTC-4, James Cammarata wrote:
>>
>> Hi all, we're happy to announce that RC2 for 2.1.2 is now available for
>> testing.
>>
>
> Any chance the road map that was promised in the 2.1 release announcement
> will be made available soon?  We are trying to upgrade our playbooks from
> 1.9.4 to 2.1.2 and I'd hate to see 2.2 come out soon afterwords and require
> yet another migration effort.
>
> TIA
>
> JOHN PEACOCK
> senior software build and release engineer
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/abcaa553-2cc9-4706-baac-9b6c3636e49e%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/abcaa553-2cc9-4706-baac-9b6c3636e49e%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFijnJy89vCKQZPixBhp16Pa9kv9LTbd5CyOTnK%3DnqWp-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.1.2 RC2 is ready for testing

[James Cammarata]

Hi nusenu, I'll take a look at that again as we will be doing a RC3 for
2.1.2.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Wed, Aug 31, 2016 at 1:32 PM, nusenu <nus...@openmailbox.org> wrote:

> Hi,
>
> are there any plans to fix regression [1] with ansible version 2.1.2?
>
>
> [1] https://github.com/ansible/ansible/issues/14829
>
> thanks,
> nusenu
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/625a78f1-20d1-0816-c97d-
> eb14a9211a9d%40openmailbox.org.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgR3ZSHZLWvkjCQEJQGJP30-ZVxnk3DkypijfBDTpfPQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 RC2 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC2 for 2.1.2 is now available for
testing.

This release candidate also adds the following fixes for bugs:

* Fixed a bug in which INI files incorrectly treated a hosts range as a
section header (#15331)
* Fixed a bug in which the max_fail_percentage calculation erroneously
caused a series of plays to stop executing (#15954)
* Fixed a bug in fetch actions which were not idempotent when the target
file was a symlink (#17255)
* Fixed a bug in which the task names were not properly templated (#16295)
* Fixed a bug causing "squashed" loops (ie. yum, apt) to incorrectly report
results (ansible-modules-core#4214)
* Fixed several bugs related to includes:
  - when including statically, make sure that all parents were also
included statically (issue #16990)
  - properly resolve nested static include paths
  - print a message when a file is statically included
* Fixed a bug in which module params expected to be float types were not
converted from integers (only strings) (#17325)


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.2.rc2.tar.gz
SHA256: 98237d2fc64f5d8af8cb9b123c040ec46093e75ec1c8804095de230580104aad

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.2.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.1.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiW8XxQ0prXwK_g%3DX1-oQtmowgiZ%2BG-A6hFqeQZ4n6Zvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.2 RC1 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC1 for 2.1.2 is now available for
testing.

This release candidate fixes many bugs, including (but not limited to):

* Fixed a bug introduced by static includes in 2.1, which prevented
notifications from going to the "top level" handler name.
* Fixed a bug where a group_vars or host_vars directory in the current
working directory would be used (and would take precedence) over those in
the inventory and/or playbook directory.
* Fixed a bug which could occur when the result of an async task did not
parse as valid JSON.
* (re)-allowed the use of ansible_python_interpreter lines with more than
one argument.
* Fixed several bugs related to the creation of the implicit localhost in
inventory.
* Fixed a bug related to an unspecified number of retries when using until.
* Fixed a race-condition bug when creating temp directories before the
worker process is forked.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.1.rc1.tar.gz
SHA256: 877595c6ae0f6a4cbf91d368aeb1194d8df65cbb084033b62dd163c2a24080d7

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.1.rc1
$ 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.1.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFh1UKSEtVxeEZr353su0S6mioY%3D2rof5yxkUd6LoOottA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Getting this error, please help.

[James Cammarata]

Hi Sanjay, could you please provide more details? Most likely this is a
password/certificate error.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Thu, Aug 18, 2016 at 2:36 PM, Sanjay Kumar <sanjay@gmail.com> wrote:

> Getting this error, please help.
>
> [sysadm@centos7 ~]$ ansible -m ping centos71
> centos71 | UNREACHABLE! => {
> "changed": false,
> "msg": "Failed to connect to the host via ssh.",
> "unreachable": true
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/a961a1ad-b97b-4a36-85b4-c13f4802008b%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/a961a1ad-b97b-4a36-85b4-c13f4802008b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgEBE%2B9%3DRvrCmHmmA3MCkeAp2pC6FHQnEZUavwi6YxtDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.0 variable precedence using an inventory file

[James Cammarata]

Generally the best place to put global vars you want to override is in role
defaults. These have the lowest priority and can be very easily overridden
by just about any other variable source, including inventory variables (so
I'm not sure what problem you're running into there). You should be able to
specify the `db_user` var in either group or host vars, or in params set on
the role as it's being run (or even --extra-vars, in the extreme case).

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Sun, Aug 14, 2016 at 4:55 PM, Joe Jasinski <joe.jasin...@gmail.com>
wrote:

> Hi all,
>
> I have a set of Ansible configuration that I intend to use as a Generic
> template for setting up a Django webserver and related services.  This
> project contains a multitude of roles for configuring various aspects
> optional services (Nginx, Django, Redis, Postgres, etc.).
>
> I'm trying to find a good way to specify good global default, overridable
> variables that can be used throughout all of my roles.  For example, I'd
> like to define variables like "app_user" or "app_name" (and many others)
> that I can use in all of my roles.
>
> Right now, these variables are placed at the top level of my project
> inside of env_vars/base.yml.  I'm thinking that this would be my global
> default configuration file that would define all of the defaults throughout
> the project and inform users of what settings are available to override.
>
> Also, the role defaults that I have defined in each role read in variables
> set in the env_vars/base.yml (my global defaults file), and set local
> copies of those variables for use in that role's tasks.
>
> # contents of roles/postgres/defaults/main.yml
> ---
> postgres__db_user: "{{ db_user }}"
>
> In that example, that global "db_user" might be used in several roles.  I
> like this approach because it's very DRY and modular; the global 'db_user'
> variable sets the namespaced local 'postgres__db_user' variable inside of
> the postgres role, but can be namespaced differently in other roles.
>
> What I'd love to be able to do is use the inventory file to override the
> global defaults. The inventory file seems like a good place to put
> variables that would customize the provisioning of specific hosts.
>
> However, the problem is that the inventory file is one of the things that
> takes least precedence in the variable precedence hierarchy.
>
> http://docs.ansible.com/ansible/playbooks_variables.
> html#variable-precedence-where-should-i-put-a-variable
>
> (I'm a bit confused by this because. I'd think the inventory file, being
> the thing that is most likely be used to create host-specific
> configurations, would take a high precedence.)
>
> I'm wondering if there is a better way to organize my project such that I
> can set some global defaults that can be the defaults for all roles, retain
> modular roles with the namespaced variables, but be able to cleanly
> configure any non-defaults in the inventory.
>
> Does anyone know how I might achieve this or know of any other best
> practices for situations like this?
>
> Note: I'm currently using the --extra-vars command line switch to pass in
> variables that I want to override, but this makes for really long command
> line executions.
>
> Here is my project thus far to see a working example:
> https://github.com/JoeJasinski/ansible-django-stack
>
> Thanks for any advice,
>
> Joe
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/ansible-project/29b46d5d-c57d-4482-a711-61d5928c96e8%40googlegroups.
> com
> <https://groups.google.com/d/msgid/ansible-project/29b46d5d-c57d-4482-a711-61d5928c96e8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjET9JxiNsS%3DdA5yiM34OvnUtBASS7jRuQ59YuXRmUV0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.1.0-1 FINAL has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.1.1 has been released!

This release fixes many bugs, summarized here from previous RC emails:

* 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.
* Several fixes to the way async works to prevent race conditions and other
bugs
* More fixes to the way failed and unreachable hosts affect future plays
* Fixed a bug in the way the to_json filter encoded some objects
* Fixed a bug in the way roles and dependencies are loaded, and how they
inherit params from parent roles.
* Fixed a bug in which the number of retries in a do/until loop was off by
one
* Fixed a bug in the way the passwd lookup deals with salts
* When using the local connection, internally the remote_user value is now
forced to be the current user even if remote_user is specified, to prevent
issues with become settings
* Fix for Azure modules to work with most recent Azure python library
(2.0.0rc5)
* Fix for bug related to unreachable hosts and any_errors_fatal in the
linear strategy
* Fix for error handling in relation to killed/dead worker processes. If
workers are killed via SIGKILL or SIGTERM, this will halt execution of the
playbook.
* Fixed a regression in the way we handle variables from dependent roles.
* Added better handling for certain errors thrown from the cryptography.
* Fixed a typo in the azure_rm_storageaccount module.
* Fixed some minor bugs in the os_user_role and cs_volume modules.
* Fixed a bug related to the return value of a low-level inventory API call
related to getting variables for hosts and groups.
* Many modules bugs.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

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 the version of Ansible you're running.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjSgBvuSMSaebRQC22dVQQQDwESincr7FfNY770Gbe6Rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.1 RC5 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC5 for 2.1.1 is now available for
testing.

This release candidate adds in one more patch, which restores some
functionality provided by
an internal API method related to getting variables for hosts and groups.
We wanted to get this
in before the 2.1.1 final release so some external projects using this
method continued to work.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.1.0-0.5.rc5.tar.gz
SHA256: 2e6dbe03098f860e1b1829546d2dbbb6d617d2884c008372d40278f863541c3f

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.1.0-0.5.rc5
$ 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.1.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi%3DjeqXGOAbCNO6rinaoyzv46_nzgYmP92x7aB4of-Oew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.1 RC4 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC4 for 2.1.1 is now available for
testing.

This release candidate fixes several more bugs since the RC3 release:

* Fixed a regression in the way we handle variables from dependent roles.
* Added better handling for certain errors thrown from the cryptography.
* Fixed a typo in the azure_rm_storageaccount module.
* Fixed some minor bugs in the os_user_role and cs_volume modules.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.1.0-0.4.rc4.tar.gz
SHA256: a10ae8a25db27c63d53b5dac39f36620c301be66ad810251667f2f7cf6527e44

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.1.0-0.4.rc4
$ 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.1.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhNmEeONw5K%2B2p4qZR8_ZqVVknsqtTWeH-_PtMeVfcwpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.1 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.1.1 is now available for
testing.

This release candidate fixes several more bugs since the RC2 release:

* Fix for Azure modules to work with most recent Azure python library
(2.0.0rc5)
* Fix for bug related to unreachable hosts and any_errors_fatal in the
linear strategy
* Fix for error handling in relation to killed/dead worker processes. If
workers are killed
  via SIGKILL or SIGTERM, this will halt execution of the playbook.


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.1.0-0.3.rc3.tar.gz
SHA256: 0e06a2ce363793dd0eff139425364c57b2ff2279a9fc6d2614aac0fe23f3adf1

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.1.0-0.3.rc3
$ 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.1.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi7_zT5zgQe_%2BrzDRVU7cYZsVz8XLL8DcqbjH01bd7QLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.1 RC1 is ready for testing

[James Cammarata]

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?
--

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

http://releases.ansible.com/ansible/ansible-2.1.1.0-0.1.rc1.tar.gz
SHA256: 93c16857edefd843ad0dda5f69a8975676e17634a549617ec08fb085dee8fda3

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.1.0-0.1.rc1
$ 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.1.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgSkMep--Gd_%3Diwd3-2xrSG_yKnk8WSLNOK5borKTuq2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.0.0-1 FINAL has been released!

[James Cammarata]

Hi all, we're very happy to announce that Ansible 2.1 has been released!

On the networking front, we’ve included managing networking infrastructure
as first-order feature set in Ansible--no separate download required. We
previously released the Networking tech preview in February at AnsibleFest
in London, and now it is fully integrated into Ansible as part of 2.1
Ansible’s agentless model works particularly well in the network management
space, and with a lot of help and support from the vendors, we are very
pleased to have our first major release with support for these features.
Networking now includes support for:

   - Cisco
   - HP Enterprise
   - Juniper
   - Arista Networks
   - Cumulus Networks

In the Microsoft world, we significantly upped our game for both Windows
and Azure Cloud. We’re happy to take the beta tag off of our Windows
support, and make it a fully supported part of the Ansible automation
platform. As part of this effort, we’ve engaged more deeply with the
pywinrm project team and others to add support for NTLM and Kerberos
delegation. NTLM makes managing domain resources much easier, since domain
users can authenticate with just a username and password, which is enabled
by default in WinRM. Kerberos delegation allows for easy domain-based
multi-hop management (eg, accessing file shares and SQL Server databases
with domain credentials). For Azure, we’ve added a full suite of modules,
as well as an inventory script that targets the new Azure Resource Manager
API. The new modules allow first-class management of most basic resource
types (eg, virtual networks, storage accounts, NICs, virtual machines), as
well as deployment of Azure Resource Manager templates. We’ve also built a
shared framework for supporting new Azure resource types, so it’s much
easier for the Ansible community to keep up with changes to the Azure
platform, and to wrap custom resources in Ansible modules.

On the containers front, our focus for this release is to further mature
our Docker support, with a large effort in making it simple to manage and
scale Docker infrastructure--especially as it relates to your overall
infrastructure. We really focused on our core mission of “radically simple
automation,” and I think we’ve done well. Here are some basics about what’s
new in container-world:

   - docker_service: Allows users to consumer Docker Compose and manage and
   scale multiple services in a standalone environment or Docker Swarm.

In addition to all of these new features, many improvements have been made
to fix backwards compatibility issues with 1.9, so the transition to 2.1
should be a bit smoother for many users.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhDLHDLeVj98XSDgHjz52rysSc%2B8jP_rTxJJ7Ba1vi6HA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.0 RC4 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC4 for 2.1.0 is now available for
testing.

This updated release candidate fixes two more bugs (one very long standing
and one a result of a change in this release):

* Fixes a bug where the item squashing code (which is used by many package
modules) was incorrectly
  squashing the list of package names.
* Adds an additional mitigation for the intermittent ssh issue where a
heavily loaded system
  might return no data (this is a bug between sshd and the kernel, but this
mitigation makes it
  much less likely to occur).

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.0.0-0.4.rc4.tar.gz
SHA256: 09e52279748dc2a4b6b67d8343a65afb911df63b7d4af91dacdf0b607ba276a2

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.0.0-0.4.rc4
$ 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.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiweRcrRuxv2qkRzM3-Uk9H%3DM6V%3DiiEzpMF1BGVqtu71Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.0 RC3 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC3 for 2.1.0 is now available for
testing.

This updated release candidate fixes a few additional bugs, including (but
not limited to):

* Fixed several bugs to make the execution of multiple plays (when failures
occur)
  more closely reproduce the behavior from 1.9.x.
* Added one more new docker module: docker_service, which allows you to use
Docker compose
  files from an Ansible module.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.0.0-0.3.rc3.tar.gz
SHA256: 7ac45813bd74adcc790760261eca97c85072aeff37e8581cccb04af82d7f5735

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.0.0-0.3.rc3
$ 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.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjTMK1t9B1gCV8YB%3DE9OfZGYoZ2%2BF9ZukLe%3DBUYPzoqbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Ansible 2.1.0 RC2 is ready for testing

[James Cammarata]

Hi Bernhard, sorry about that. That's been fixed now.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Wed, May 18, 2016 at 7:05 AM, Bernhard L. <lib...@gmail.com> wrote:

> Hi,
>
> $ git clone https://github.com/ansible/ansible.git
>> $ cd ansible
>> $ git checkout v2.1.0.0-0.2.rc2
>> $ git submodule update --init
>>
>
> The tag "v2.1.0.0-0.2.rc2" is missing in the github repo. Latest tag is
> "v2.1.0.0-0.1.rc1".
>
> --
> 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-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhUCS-FD_fJOu%3Dap75ZxBEmBBut3yeCB27zQyhk3oBqag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.1.0 RC2 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that RC2 for 2.1.0 is now available for
testing.

This updated release candidate fixes several bugs from RC1, including (but
not limited to):

* Fixed several bugs related to the new ziploader method of executing
modules on
  remote systems.
* Fixed several bugs in strategies and with task iteration.
* Fixed a bug where "meta: refresh_inventory" was failing due to a host
filtering pattern
* Fixed a bug where blocks with an "always" portion but no "rescue" were
improperly
  continuing after a failed task in the block.
* Fixed a bug with the combined use of set_fact and run_once.
* Fixed retry/until logic, where a task succeeding on the last iteration of
the retry
  would still be marked as failed regardless of success.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.1.0.0-0.2.rc2.tar.gz
SHA256: a4410614afb5ce2b355b3b8f7321c5e7006d4eaf2673553b50d3afdfe1386d7e

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.0.0-0.2.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.1.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgd-9fwhjdTF4dSOzqY%2Bimze3kq17vwpYSUF7pDKsxDEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Agenda for Public Core Meeting - 2016-04-21 @ 15:00 UTC

[James Cammarata]

If you have a topic/issue/PR you wish to discuss, you can add it as a
comment here so we can keep track of things. If you don't show up for the
meeting, your issue will be skipped and dropped, so please be sure to
attend if you add something.

https://github.com/ansible/community/issues/83

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjCb7eyhYbN9asAbstXysTur-_iOY0GqmpuX%2BAKBkyiqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.2.0 has been released

[James Cammarata]

Hi all, 2.0.2.0 has been released, and is now available.

This release continues to fix bugs introduced in the 2.0 release, as well
as one security bug:

* SECURITY: Fix lxc_container module having predictable temp file names and
setting file
  permissions on the temporary file too leniently on a temporary file that
was
  executed as a script.  Addresses CVE-2016-3096
* Fixed bugs related to the iteration of tasks when certain combinations of
roles,
  blocks, and includes were used, especially when handling errors in
rescue/always
  portions of blocks.
* Fixed some bugs in the URI module related to redirects and SSL handling.
* Fixed some bugs related to the incorrect creation of extra temp
directories for
  uploading files, which were not cleaned up properly.
* Fixed a bug related to the variable precedence of role parameters,
especially when
  a role may be used both as a dependency of a role and directly by itself
within the
  same play.
* Fixed some bugs in the 2.0 implementation of do/until.
* Fixed some bugs related to run_once:
  - Ensure that all hosts are marked as failed if a task marked as run_once
fails.
  - Show a warning when using the free strategy when a run_once task is
encountered, as
there is no way for the free strategy to guarantee the task is not run
more than once.
* Fixed a bug where the assemble module was not honoring check mode in some
situations.
* Fixed a bug related to delegate_to, where we were incorrectly using
variables from
  the inventory host rather than the delegated-to host.
* The 'package' meta-module now properly squashes items down to a single
execution (as the
  apt/yum/other package modules do).
* Fixed a bug related to the ansible-galaxy CLI command dealing with paged
results from
  the Galaxy server.
* Pipelining support is now available for the local and jail connection
plugins, which is
  useful for users who do not wish to have temp files/directories created
when running
  tasks with these connection types.
* Improvements in support for additional shell types.
* Improvements in the code which is used to calculate checksums for remote
files.
* Some speed ups and bug fixes related to the variable merging code.
* Workaround bug in python subprocess on El Capitan that was making vault
fail
  when attempting to encrypt a file
* Fix a bug in the uri module where setting headers via module params that
  start with HEADER_ were causing a traceback.
* Fix bug in the free strategy that was causing it to synchronize its
workers
  after every task (making it a lot more like linear than it should have
been).


As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

Thanks, and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFj3-UrqHa1V3e%2BCfMGChehX229T61DGBat6%3DF2vMbmgkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 1.9.6-1 has been released

[James Cammarata]

Hi all, we're happy to announce that 1.9.6-1 has been released.

As noted in the RC1 announcement, 1.9.6 fixes a few bugs introduced in the
1.9.5 release, as well as a security flaw:

* Fixes several security bugs in the lxc_container module, which could
result in someone with local privileges modifying a script which was being
created with world-writable permissions, resulting in that new script being
run with root permission. If you're using this module, you should upgrade
immediately.
* Fixes a bug where --limit was incorrectly affecting inventory variables
being read.
* Fixes a bug where a role parameter named 'name' would incorrectly be used
as the name of the role.

As always, this update is available via PyPi and releases.ansible.com now.
Packages for other distros will be available as soon as possible.

Thanks and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjCavNp%2B0P74gNy4csOL3dZp6SncMf4PeMG9ppjuDdbOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.2 RC4 is available for testing

[James Cammarata]

Hi all, we have released Ansible 2.0.2 RC4 to address a few more last
minute bugs:

* A very rare yet nagging issue (
https://github.com/ansible/ansible/issues/15342), which appears to be
related to a bug in certain versions of sshd itself. The fix for this
minimizes the potential situations in which this bug occurs, though we may
look at fixing this further in 2.1.0.
* A bug in the free strategy where it was incorrectly waiting for all
pending results to come in, thus effectively making it behave like the
linear strategy.
* A bug in win_user.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.0.2.0-0.4.rc4.tar.gz
SHA256: b902f974b48bd6867fc5e6770bbc80df5d8af6c5b8f5a831bc8611360af1dc08

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.0.2.0-0.4.rc4
$ 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.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgeTx89xCrssgRpPbVG_edfzKeZFjkKmH1MOwK60YZ%3Dbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible Core Public Meetings

[James Cammarata]

Hi all,

The core team will be resuming our public team meetings starting tomorrow,
however with a bit of a change in format.

Previously we had done them on a public hangout, we're now going to be
holding our meetings in #ansible-meeting on Freenode. For those who have
seen the Community meetings held by Robyn/Greg that shouldn't be too
surprising. We're recording these and publish them after, so anyone who is
not able to attend can view the minutes/takeaways/etc.

We will also be holding two meetings per week for one hour, as opposed to
one two-hour meeting, which will help us cover a bit wider range of times,
for those in Europe/Asia:

Tuesdays: 3PM EST/EDT
Thursdays: 11AM EST/EDT

For those who had not attended one of our previous meetings, we generally
intend this to be a time when anyone with an interest in a bug or PR
(whether they own it or not) to get us to review it and hopefully get it
fixed/merged in more quickly. This first meeting tomorrow, most likely
we'll also be doing some house-keeping, figuring out what the agenda of
each meeting will be, etc. Be sure to swing by if you want a voice in that!

If you have any questions, please let us know, or drop by #ansible-devel on
Freenode.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhyH4WL13KesJ%3D8_Rx0cM%3DsiRArYcW3%3DUH6KZ2qB7a-Mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 1.9.6 RC1 and 2.0.2 RC3 are available for testing

[James Cammarata]

Hi all, we're happy to announce a twofer:

Ansible 1.9.6 RC1 is available for testing, and fixes a couple of bugs
introduced by the 1.9.5 release:

* Fixes several security bugs in the lxc_container module, which could
result in someone with local privileges modifying a script which was being
created with world-writable permissions, resulting in that new script being
run with root permission.
* Fixes a bug where --limit was incorrectly affecting inventory variables
being read.
* Fixes a bug where a role parameter named 'name' would incorrectly be used
as the name of the role.

Ansible 2.0.2 RC3 likewise includes the fix for the lxc_container bug, as
well as another minor bug related to using hostvars in a delegated action
(which includes the use of local_action).

Ansible 2.0.2 RC3 can be downloaded here:

http://releases.ansible.com/ansible/ansible-2.0.2.0-0.3.rc3.tar.gz
SHA 256: ad99714b00f9de32b76046f96d2d773f9867be6a9506e266dbc3282b6efaced7

Ansible 1.9.6 RC1 can be downloaded here:
http://releases.ansible.com/ansible/ansible-1.9.6-0.1.rc1.tar.gz
SHA 256: ed65bc79788898fc91f68671f49eee41ce2ae40ba722f9584c91967f63f47929

If you discover any errors in either of these release candidates, please
open a Github issue and be sure to mention you're testing against this
release candidate.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgmhAuY2vdVaQnT1JxJhvLbsw2pUWUkaTkrd0JvFvvKeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.2 RC2 is ready for testing

[James Cammarata]

Hi all, we're happy to announce that the first release candidate for 2.0.2 is
now available for testing.

This updated release candidate fixes several bugs from RC1, as well as
fixes a few additional bugs we wanted to include in 2.0.2:

* Fixed a bug related to using non-ASCII characters in inventory patterns.
* Fixed bugs related to task includes and role dependencies.
* Fixed bugs related to --start-at-task.
* Fixed a bug related to splitting module arguments when quotes are used
inside jinja2 variables.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.0.2.0-0.2.rc2.tar.gz
SHA256: 06f9d0c276d732ffcb7dc4e671c5e934df2c7a397b8d16c26f8351eaa68d143c

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.0.2.0-0.2.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.2
.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFh-o2UbsDRA9Ro%3DFOBN%3DPHuH7xMCF13b3Jzt4B5bRZvmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Correct quoting of arguments for raw module

[James Cammarata]

That should be fixed in the latest versions of devel/stable-2.0.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Thu, Mar 31, 2016 at 4:07 AM, Johannes Kastl <m...@ojkastl.de> wrote:

> On 31.03.16 at 01:04 Uditha Desilva wrote:
> > Quoting the "=" seems to do the trick at least in my trivial test:
> >
> > $ ansible -v -m raw -a 'env -i ABC\=blah /usr/bin/printenv' localhost
> > Using /etc/ansible/ansible.cfg as config file
> > localhost | SUCCESS | rc=0 >>
> > ABC=blah
>
> Interesting, I did not think of the equal sign being the problem. I'll
> run some tests against a FreeBSD host and report back...
>
> Johannes
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/56FCDAB7.5030607%40ojkastl.de
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhhYeAtpO9j%2BUMOy9bT%2Bd1L%3DQJjn7YC4Tfu%3DyzWuXA6mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Error in yum module

[James Cammarata]

If you run it without check mode enabled, does it install the package?

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Thu, Mar 31, 2016 at 6:14 AM, Mario Polario <mario.pran...@gmail.com>
wrote:

> Hi!
>
> I installed ansible-1.9.4-1.el7.noarch from EPEL repository on RHEL 7.2.
>
> I have several test servers to manage.
>
> I tried simple playbook:
>
>
>
>
>
>
>
> * hosts: webservers   remote_user: root  tasks:  - name: install
> vimyum: name=vim state=latest*
>
> Trying to execute gives me error:
> # ansible-playbook --verbose vim.yml --check
>
> PLAY [webservers]
> *
>
> GATHERING FACTS
> ***
> ok: [lvdansk1.vipnet.hr]
> ok: [lvdansk2.vipnet.hr]
>
> TASK: [install vim]
> ***
>
>
>
> *failed: [lvdansk1.vipnet.hr <http://lvdansk1.vipnet.hr>] => {"changed":
> false, "failed": true, "rc": 0, "results": []}msg: No Package matching
> 'vim' found available, installed or updatedfailed: [lvdansk2.vipnet.hr
> <http://lvdansk2.vipnet.hr>] => {"changed": false, "failed": true, "rc": 0,
> "results": []}msg: No Package matching 'vim' found available, installed or
> updated*
>
> FATAL: all hosts have already failed -- aborting
>
> PLAY RECAP
> 
>to retry, use: --limit @/root/vim.retry
>
> lvdansk1.vipnet.hr : ok=1changed=0unreachable=0
> failed=1
> lvdansk2.vipnet.hr : ok=1changed=0unreachable=0
> failed=1
>
> Managed nodes can normally install vim via "yum install vim" when done by
> hand. It does not make sense.
>
> Any idea how to troubleshoot this issue?
>
> Thank you!
>
> Best regards,
>
> Mario.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/e2886547-7935-4292-8395-ca762d68ab9d%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/e2886547-7935-4292-8395-ca762d68ab9d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjwYO8PLOfmb8HTU5%2BD2oLt6ZnPKc78WgdjE1j8%3D1M9Ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.2.0 RC1 is available for testing

[James Cammarata]

Hi all, we're happy to announce that the first release candidate for 2.0.2
is now available for testing.

This release candidate includes fixes for many bugs, as well as a few other
improvements:

* Backport of the 2.1 feature to ensure per-item callbacks are sent as they
occur,
  rather than all at once at the end of the task.
* Fixed bugs related to the iteration of tasks when certain combinations of
roles,
  blocks, and includes were used, especially when handling errors in
rescue/always
  portions of blocks.
* Fixed handling of redirects in our helper code, and ported the uri module
to use
  this helper code. This removes the httplib dependency for this module
while fixing
  some bugs related to redirects and SSL certs.
* Fixed some bugs related to the incorrect creation of extra temp
directories for
  uploading files, which were not cleaned up properly.
* Improved error reporting in certain situations, to provide more
information such as
  the playbook file/line.
* Fixed a bug related to the variable precedence of role parameters,
especially when
  a role may be used both as a dependency of a role and directly by itself
within the
  same play.
* Fixed some bugs in the 2.0 implementation of do/until.
* Fixed some bugs related to run_once:
  - Ensure that all hosts are marked as failed if a task marked as run_once
fails.
  - Show a warning when using the free strategy when a run_once task is
encountered, as
there is no way for the free strategy to guarantee the task is not run
more than once.
* Fixed a bug where the assemble module was not honoring check mode in some
situations.
* Fixed a bug related to delegate_to, where we were incorrectly using
variables from
  the inventory host rather than the delegated-to host.
* The 'package' meta-module now properly squashes items down to a single
execution (as the
  apt/yum/other package modules do).
* Fixed a bug related to the ansible-galaxy CLI command dealing with paged
results from
  the Galaxy server.
* Pipelining support is now available for the local and jail connection
plugins, which is
  useful for users who do not wish to have temp files/directories created
when running
  tasks with these connection types.
* Improvements in support for additional shell types.
* Improvements in the code which is used to calculate checksums for remote
files.
* Some speed ups and bug fixes related to the variable merging code.
* Workaround bug in python subprocess on El Capitan that was making vault
fail
  when attempting to encrypt a file


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.0.2.0-0.1.rc1.tar.gz
SHA256: 37346865fc6ef93fd14be6d3df4a3a7715d371a07fc6d9641e6311025d06d306

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.0.2.0-0.1.rc1
$ 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.2.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

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiz%3D17ntsrb2_hz6yUJmhO71eDvaYTK1fGuet63jr98qQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 1.9.5-1 has been released

[James Cammarata]

Hi all, we're very happy to announce that Ansible 1.9.5-1 has been released.

This release to the 1.9.x series addresses several critical bugs for those
who are unable to update to Ansible 2.0. The fixes included are:

* Compatibility fix with docker 1.8.
* Fix a bug with the crypttab module omitting certain characters from the
name of the device
* Fix bug with uri module not handling all binary files
* Fix bug with ini_file not removing options set to an empty string
* Fix bug with script and raw modules not honoring parameters passed via
yaml dict syntax
* Fix bug with plugin loading finding the wrong modules because the suffix
checking was not ordered
* Fix bug in the literal_eval module code used when we need python-2.4
compat
* Added --ignore-certs, -c option to ansible-galaxy. Allows ansible-galaxy
to work behind a proxy
  when the proxy fails to forward server certificates.
* Fixed bug where tasks marked no_log were showing hidden values in output
if
  ansible's --diff option was used.
* Fix bug with non-english locales in git and apt modules
* Compatibility fix for using state=absent with the pip ansible module and
pip-6.1.0+
* Backported support for ansible_winrm_server_cert_validation flag to
disable cert validation on Python 2.7.9+ (and support for other passthru
args to pywinrm transport).
* Backported various updates to user module (prevent accidental OS X group
membership removals, various checkmode fixes).

As always, this update is available via PyPi and releases.ansible.com now.
The ansible-1.9 PPA has also been updated, and packages for other distros
will be available as soon as possible.

Thanks and enjoy!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjZcijGo8ADZdgrbVVtaMODnmX8NHEU%2BHWA0B9KC4ZJuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] How to trace/debug Ansible EC2 ?

[James Cammarata]

Since the ec2 modules use boto, which doesn't really execute commands, your
best bet is to run your playbook with the environment variable
ANSIBLE_KEEP_REMOTE_FILES=1 set, and with -vvv. This will allow you to
examine the modules left on the target system (most likely localhost) and
run them directly with your Python debugging method of choice (epdb, etc.).

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Wed, Mar 16, 2016 at 3:13 AM, Tzach Livyatan <tz...@cloudius-systems.com>
wrote:

> Hello
> I have a problem with a simple Ansible playbook which launch an EC2
> instance.
> The instance configuration is slightly different (different
> block-device-mapping) when I launch the same AMI from EC2 dashboard.
> To debug, I would like to see the exact AWS command Ansible/Boto runs.
> ansible-playbook -vvv option does not provide it, how can I go deeper into
> the code and traces?
>
> Thanks
> Tzach
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/8b3563dd-5325-464f-be7b-21e9c16ad257%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/8b3563dd-5325-464f-be7b-21e9c16ad257%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhZ3n3vhZ3udPbyA4WH9O6MfYMx4uZYpRZZj-YML5XGfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Telnet

[James Cammarata]

You cannot at this time. If someone REALLY wanted to, you could write your
own connection plugin for this, however I seriously recommend against doing
so.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Wed, Mar 16, 2016 at 2:48 PM, Vivek Raj <vivira...@gmail.com> wrote:

> Can any one say how to do telnet using ansible
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/63759286-7ed5-45f2-aa03-8c2f92170f1b%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/63759286-7ed5-45f2-aa03-8c2f92170f1b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFj-kb8na4G_MHPKXKt1c4_G%3Do8cfUWGtbLU-CbA3megYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

In theory, yes we could, however that wouldn't buy us much. The problem is
that, if the include uses a variable for the file name or loop, that
variable may change of the execution of the playbook. This is particularly
common for loops, where some previously registered result is used for the
loop variable to an include.

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Tue, Mar 15, 2016 at 1:03 PM, Timothy Appnel <t...@ansible.com> wrote:

> @jimi-c: Is it possible to evaluate static includes after the setup module
> runs to gathering facts? The most common use pattern I see in users plays
> and roles are dynamic includes that define the filename based on a fact
> like ansible_os_family. Collecting the fact before evaluating includes
> would make things even more seamless for users.
>
> Timothy Appnel
> Principal Architect
> Ansible by Red Hat
>
> +1 718.404.6429 | <+1+718.404.6429> ansible.com <https://www.ansible.com/>
>
>
> GitHub: tima <https://www.github.com/tima>
>
> Twitter: @appnelgroup <https://www.twitter.com/@appnelgroup>
>
> On Tue, Mar 15, 2016 at 11:32 AM, James Cammarata <jcammar...@ansible.com>
> wrote:
>
>> On Tue, Mar 15, 2016 at 11:03 AM, Strahinja Kustudić <
>> strahin...@nordeus.eu> wrote:
>>
>>> So basically now simple includes without any loops or variables in file
>>> name will be static by default? That is great news, since most of the
>>> includes are like that and it makes them at least backward compatible with
>>> 1.x.
>>>
>>> Could anyone tell me what exactly is the difference between:
>>>
>>> - include: "{{ some_var }}.yml"
>>>   static: yes
>>>
>>>
>> In this case, the include would be processed at playbook parsing time,
>> meaning there is no inventory. As such, `some_var` would have to be
>> available in playbook vars (vars/vars_files/role vars and defaults), or
>> extra vars. Tasks and all related info would be available to things like
>> --star-at-task, --list-tags, and --list-tasks.
>>
>>
>>
>>>
>>> and
>>>
>>> - include: "{{ some_var }}.yml"
>>>   static: no
>>>
>>> Does it mean for static: yes that some_var would need to be defined
>>> statically as a var, and for static: no some_var could be defined
>>> during play execution, e.g. set_fact: some_var=something.
>>>
>>>
>> In this case, the include would not be processed until that task was hit
>> at execution time, meaning `some_var` could come from any and all available
>> variable sources in ansible. Nothing about the tasks in this file would be
>> known at compile time, and as such that information would not be available
>> for the CLI switches mentioned above.
>>
>> --
>> 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-devel+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiSXAEYUkZy7jVGAbbyN6ho7GXnHij79%3D3OjgKGMz4ufA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 11:03 AM, Strahinja Kustudić 
wrote:

> So basically now simple includes without any loops or variables in file
> name will be static by default? That is great news, since most of the
> includes are like that and it makes them at least backward compatible with
> 1.x.
>
> Could anyone tell me what exactly is the difference between:
>
> - include: "{{ some_var }}.yml"
>   static: yes
>
>
In this case, the include would be processed at playbook parsing time,
meaning there is no inventory. As such, `some_var` would have to be
available in playbook vars (vars/vars_files/role vars and defaults), or
extra vars. Tasks and all related info would be available to things like
--star-at-task, --list-tags, and --list-tasks.



>
> and
>
> - include: "{{ some_var }}.yml"
>   static: no
>
> Does it mean for static: yes that some_var would need to be defined
> statically as a var, and for static: no some_var could be defined during
> play execution, e.g. set_fact: some_var=something.
>
>
In this case, the include would not be processed until that task was hit at
execution time, meaning `some_var` could come from any and all available
variable sources in ansible. Nothing about the tasks in this file would be
known at compile time, and as such that information would not be available
for the CLI switches mentioned above.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFj4p8rn5OO9TeiU6qNa9H_7seQSu-Wi_XuTT%3D4b9K_GUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 10:19 AM, James Cammarata <jcammar...@ansible.com>
wrote:

> On Tue, Mar 15, 2016 at 10:12 AM, Jan Grant <j...@ioctl.org> wrote:
>
>> I certainly don't want to see dynamic includes go away.
>>
>
> They're definitely not going to go away :)
>
>
> Assuming the preprocessing and running code is neatly split, how about:
>>
>> 1. Preprocess "static" includes - which can be identified by the absence
>> of J2 constructs in them
>> 2. Dynamically preprocess dynamic includes and run them as currently.
>> 3. Add a "dynamic: yes" flag which optionally adds the dynamic behaviour
>> for things that look like static includes.
>>
>
> #1 is something which can be done pretty easily, if there's no loop and
> the file name contains no variables. For #3 though, I went the other way
> because to me the more tricky thing to figure out is when you see something
> like my earlier example, when you've got `- include: "{{some_var}}.yml"`,
> and you want to force it to be pre-processed instead of dynamic. This is
> why I picked the `static: yes` syntax instead of the converse.
>
> I can look at tweaking my feature branch to do the above, though this is
> why I added config options. Using variables in the include name is valid in
> 1.x, so to 2.0 those would look like dynamic includes (as they should,
> because now the variable COULD come from an inventory source as well).
>

Just pushed an update to my feature branch to implement #1 above:

https://github.com/ansible/ansible/compare/static_includes#diff-69130db4f6e9ef75876cab5ca756d9d6R118

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhrmcOD3QP%3DDkCmoN-LuSHwfeg0kKcJDf5TEZ4SY%2BwKUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 10:12 AM, Jan Grant  wrote:

> I certainly don't want to see dynamic includes go away.
>

They're definitely not going to go away :)


Assuming the preprocessing and running code is neatly split, how about:
>
> 1. Preprocess "static" includes - which can be identified by the absence
> of J2 constructs in them
> 2. Dynamically preprocess dynamic includes and run them as currently.
> 3. Add a "dynamic: yes" flag which optionally adds the dynamic behaviour
> for things that look like static includes.
>

#1 is something which can be done pretty easily, if there's no loop and the
file name contains no variables. For #3 though, I went the other way
because to me the more tricky thing to figure out is when you see something
like my earlier example, when you've got `- include: "{{some_var}}.yml"`,
and you want to force it to be pre-processed instead of dynamic. This is
why I picked the `static: yes` syntax instead of the converse.

I can look at tweaking my feature branch to do the above, though this is
why I added config options. Using variables in the include name is valid in
1.x, so to 2.0 those would look like dynamic includes (as they should,
because now the variable COULD come from an inventory source as well).

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFg0TCDuRS%2B4Z-_P02ayLOLeEYAzdCBRTfnNr7Ykk6GWUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 4:37 AM, Strahinja Kustudić <strahin...@nordeus.com>
wrote:

> On Tue, Mar 15, 2016 at 7:12 AM, James Cammarata <jcammar...@ansible.com>
> wrote:
>
>> Because we do not load the included file until we reach that point in the
>> execution, we no longer know anything about the tasks contained within that
>> file. This means that we don't know about tags on those tasks, and
>> notifying handlers within those files do not work either (which breaks a
>> common use case for many people).
>>
>
> Your reply basically sums up my answer above. Include was broken with 2.0
> for a common use case for many people and now you would like to fix it by
> making all those people change their playbooks for it to work as they
> expected it to work in the first place, because of an uncommon use case
> which didn't even work in older versions.
>

No, the entire point of the config options is to allow users to switch to
2.0 without having to change their playbooks when moving from 1.x. Include
loops were not an uncommon use-case, in the 1.5 years or so since we
removed the capability, that was one of the most often requested features,
which is why we implemented dynamic includes in 2.0 (to make them actually
work like people expected).

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFizYLJW58vEZXN6BmsgdhhCdFJL2cdo6KGnf83bskxiRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 8:10 AM, Udondan  wrote:

> I also agree it would have made more sense if the dynamic include was
> optional and the default behavior was the version 1 way. But I also see how
> this is hard to justify now that Ansible 2 works as it does, it's hard to
> go back. If Ansible follows semver that would actually mean we have Ansible
> 3 knocking on our door if the behavior is switched back.
>
> Ideally, in my opinion, the new functionality would have been added with a
> different name, for example "import" instead of "include". This would have
> allowed a clean way to migrate without breaking things. It also makes it
> possible to distinguish between two complete different features by name.
>


Agreed, hind sight is 20/20. That is also something we considered, however
again at this point it would break playbooks as written for 2.0.



> We have adopted Ansible 2 but I would not mind if the behavior changed
> back to the old static include. In any case, I will adjust our roles. Most
> of the includes do not need to be dynamic and I would set them to static
> just to get rid of the hundreds blue include statements during playtime.
>
> Now, I'm wondering what happens if a static include includes a file which
> has a dynamic include. :)
>

Thanks for this, this is something I need to test with my feature branch. I
don't think I recursively parse tasks brought in from static includes...

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi-%2B1B9wNpazV%3DnoY%3DhY_%2Bpsdyh98c8XZ53zpRcd4KmBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

No, we can't do this because of variables and the possibility that they
will do loops (which may also be based on a variable).

Take for exampe:

- include: "{{ansible_distribution|lower}}.yml"

^ This is completely valid in 2.0, and a much nicer alternative to the
include/when syntax you used to have to do. However, we don't know which
files will be brought in until that's actually run, so we can't pre-process
anything (unless we also read in and parse every yaml file in the
playbook/roles path, which presents other problems).


James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

On Tue, Mar 15, 2016 at 7:33 AM, haad <haa...@gmail.com> wrote:

> Hi,
>
> Wouldn't be easier to just preproccess those files at beginning of
> playbook run (so you will evaluate everything to true and load all
> includes/plays/roles into memory at beginning). So you know what
> tags/handlers are inside and when that's done you just execute tasks one by
> one ?
>
> On Tue, Mar 15, 2016 at 7:12 AM, James Cammarata <jcammar...@ansible.com>
> wrote:
>
>> On Tue, Mar 15, 2016 at 1:19 AM, Mark Kusch <mark.ku...@gmail.com> wrote:
>>
>>> What issues are there with dynamic includes except for included files
>>> which do not do anything?
>>>
>>
>> Because we do not load the included file until we reach that point in the
>> execution, we no longer know anything about the tasks contained within that
>> file. This means that we don't know about tags on those tasks, and
>> notifying handlers within those files do not work either (which breaks a
>> common use case for many people).
>>
>>
>>>
>>> If there was such a huge problem to discuss this, I wouldn't go for a
>>> change in behaviour of include itself but add a new plugin, e.g.
>>> static_include, or include_static.
>>>
>>> Inline...
>>>
>>> # kraM
>>>
>>> On 21:57 Mon 14 Mar, James Cammarata wrote:
>>> > On Mon, Mar 14, 2016 at 8:22 PM, Strahinja Kustudić <
>>> strahin...@nordeus.eu>
>>> > wrote:
>>> >
>>> > > I like the idea, but I don't like the proposal. I would do the same
>>> thing,
>>> > > but the other way around. With your proposal it would break backward
>>> > > compatibility with 1.9 if you don't update all your includes, or
>>> update
>>> > > ansible.ini. Also most of the includes are static anyway (since
>>> dynamic
>>> > > ones didn't work pre 2.0), so why not make them all static by
>>> default.
>>> > >
>>> >
>>> > I went this way to avoid introducing problems with those who have
>>> already
>>> > adopted 2.0. We discussed this internally in depth, and flipping the
>>> > defaults would break everyone who was using 2.0 and upgrading to 2.1.
>>> We
>>> > feel at this point that most people who have not upgraded are avoiding
>>> > doing so because of backwards incompatibilities with 2.0, so this is
>>> mainly
>>> > targeted at giving them an upgrade path.
>>>
>>> Upgraded everything to 2.0.0.2, currently upgrading everything to 2.0.1.0
>>> (deprecation warnings not visible due to a bug in 2.0.0.2). If we need to
>>> update everything for 2.1.0, ... Where would that lead to?
>>>
>> >
>>> >
>>> > > My proposal is to make all includes static by default and introduce
>>> a new
>>> > > keyword *dynamic: yes* (or use *static: no* if you like it more)
>>> which
>>> > > you would set on includes where you need them to be dynamic. This
>>> would
>>> > > make old 1.9 playbooks backward compatible without any changes
>>> anywhere,
>>> > > and if you need a dynamic include in a 2.0 playbook, you will need to
>>> > > change it in just a few places (since there are far less 2.0
>>> playbooks
>>> > > anyway and even lower number of dynamic includes).
>>> > >
>>> >
>>> > Again, this is something we discussed internally, the option name is
>>> > flexible and we can flip it. However for the reasons above we'd
>>> default it
>>> > to `dynamic: yes`.
>>>
>>> --
>> 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-devel+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
>
> Regards.
>
> Adam
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFijLOjQhT8mWnbx21cFULXxfjApwCpQmVw7WEqroNg%2BkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Tue, Mar 15, 2016 at 1:19 AM, Mark Kusch <mark.ku...@gmail.com> wrote:

> What issues are there with dynamic includes except for included files
> which do not do anything?
>

Because we do not load the included file until we reach that point in the
execution, we no longer know anything about the tasks contained within that
file. This means that we don't know about tags on those tasks, and
notifying handlers within those files do not work either (which breaks a
common use case for many people).


>
> If there was such a huge problem to discuss this, I wouldn't go for a
> change in behaviour of include itself but add a new plugin, e.g.
> static_include, or include_static.
>
> Inline...
>
> # kraM
>
> On 21:57 Mon 14 Mar, James Cammarata wrote:
> > On Mon, Mar 14, 2016 at 8:22 PM, Strahinja Kustudić <
> strahin...@nordeus.eu>
> > wrote:
> >
> > > I like the idea, but I don't like the proposal. I would do the same
> thing,
> > > but the other way around. With your proposal it would break backward
> > > compatibility with 1.9 if you don't update all your includes, or update
> > > ansible.ini. Also most of the includes are static anyway (since dynamic
> > > ones didn't work pre 2.0), so why not make them all static by default.
> > >
> >
> > I went this way to avoid introducing problems with those who have already
> > adopted 2.0. We discussed this internally in depth, and flipping the
> > defaults would break everyone who was using 2.0 and upgrading to 2.1. We
> > feel at this point that most people who have not upgraded are avoiding
> > doing so because of backwards incompatibilities with 2.0, so this is
> mainly
> > targeted at giving them an upgrade path.
>
> Upgraded everything to 2.0.0.2, currently upgrading everything to 2.0.1.0
> (deprecation warnings not visible due to a bug in 2.0.0.2). If we need to
> update everything for 2.1.0, ... Where would that lead to?
>
>
> >
> > > My proposal is to make all includes static by default and introduce a
> new
> > > keyword *dynamic: yes* (or use *static: no* if you like it more) which
> > > you would set on includes where you need them to be dynamic. This would
> > > make old 1.9 playbooks backward compatible without any changes
> anywhere,
> > > and if you need a dynamic include in a 2.0 playbook, you will need to
> > > change it in just a few places (since there are far less 2.0 playbooks
> > > anyway and even lower number of dynamic includes).
> > >
> >
> > Again, this is something we discussed internally, the option name is
> > flexible and we can flip it. However for the reasons above we'd default
> it
> > to `dynamic: yes`.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi8%2BEEeZ35h50XgUfMPX4PDmCDvo%2BXeDhaDhwbrAXVDtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Re: [ansible-devel] Re: Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

On Mon, Mar 14, 2016 at 8:22 PM, Strahinja Kustudić 
wrote:

> I like the idea, but I don't like the proposal. I would do the same thing,
> but the other way around. With your proposal it would break backward
> compatibility with 1.9 if you don't update all your includes, or update
> ansible.ini. Also most of the includes are static anyway (since dynamic
> ones didn't work pre 2.0), so why not make them all static by default.
>

I went this way to avoid introducing problems with those who have already
adopted 2.0. We discussed this internally in depth, and flipping the
defaults would break everyone who was using 2.0 and upgrading to 2.1. We
feel at this point that most people who have not upgraded are avoiding
doing so because of backwards incompatibilities with 2.0, so this is mainly
targeted at giving them an upgrade path.


> My proposal is to make all includes static by default and introduce a new
> keyword *dynamic: yes* (or use *static: no* if you like it more) which
> you would set on includes where you need them to be dynamic. This would
> make old 1.9 playbooks backward compatible without any changes anywhere,
> and if you need a dynamic include in a 2.0 playbook, you will need to
> change it in just a few places (since there are far less 2.0 playbooks
> anyway and even lower number of dynamic includes).
>

Again, this is something we discussed internally, the option name is
flexible and we can flip it. However for the reasons above we'd default it
to `dynamic: yes`.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhyn41cwcYO5VH9CaPrAj8T6zHwzECNa328DEYzNYij-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Proposal for fixing playbooks with dynamic include problems

[James Cammarata]

Hi all, we've been working on a solution over the last few weeks to address
the problems introduced by making includes dynamic in 2.0, and would like
some community feedback on my ideas.

As you're all probably well aware by now, we moved task-level includes to
be completely dynamic in 2.0 to make doing things like loops easier. In
1.9.x and before, includes functioned like pre-proccessor statements - the
files were parsed, turned into a list of tasks, and inserted into the main
list of tasks at the time the main playbook or role was parsed.

The downside to this move was to make it quite difficult to handle certain
situations, as we now know nothing about those files (and specifically what
tasks are in those files) until we encounter them in the regular execution
of the playbook. As such, we don' t know what tags are there, and when
notifying handlers the task names aren't known so the notifications fail.

To address this shortcoming, our idea was simple: allow includes to be
marked as static, and as such they again function as pre-processor
statements. Here is the feature branch where we implement this change:

https://github.com/ansible/ansible/compare/static_includes

In a nutshell, there are now two ways to make includes behave as they did
in 1.9.x:

1. Use the `static: true` option on the include.
2. Set options in your ansible.cfg. There is one option each for regular
tasks, and one for handlers, as some may wish to make all handler includes
static without impacting those in regular task sections.

Example:

- hosts: all
  gather_facts: yes
  tasks:
  - include: foo.yml
static: yes

Or, if you're migrating from 1.9.x (or earlier) to 2.0 and want all of your
includes to work as they did before, add the following two options to your
ansible.cfg in the [defaults] section:

task_includes_static = yes
handler_includes_static = yes

The caveat to all of this is of course that using loops on a static include
will no longer work. Also, any playbook marked as static using variables
must have those variables available at compile time (no inventory sources
are available at this point).

We're looking at merging this in for the 2.1 release (targeting an April
release), so any comments/ideas for making it work better are appreciated.
If you've avoided the 2.0 release because of the impact of dynamic
includes, we'd really love to hear how your playbooks work (or don't) when
using this feature branch with dynamic includes disabled completely.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhRRpR%2Bai7iymX%2B%2B7hK-Evv3XiuKFqWd7xcyH9FJvmVFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 1.9.5 RC1 is available for testing

[James Cammarata]

Hi all, Ansible 1.9.5 RC1 is available for testing.

This release to the 1.9.x series addresses several critical bugs for those
who are unable to update to Ansible 2.0. The fixes included are:

* Compatibility fix with docker 1.8.
* Fix a bug with the crypttab module omitting certain characters from the
name of the device
* Fix bug with uri module not handling all binary files
* Fix bug with ini_file not removing options set to an empty string
* Fix bug with script and raw modules not honoring parameters passed via
yaml dict syntax
* Fix bug with plugin loading finding the wrong modules because the suffix
checking was not ordered
* Fix bug in the literal_eval module code used when we need python-2.4
compat
* Added --ignore-certs, -c option to ansible-galaxy. Allows ansible-galaxy
to work behind a proxy
  when the proxy fails to forward server certificates.
* Fixed bug where tasks marked no_log were showing hidden values in output
if
  ansible's --diff option was used.
* Fix bug with non-english locales in git and apt modules
* Compatibility fix for using state=absent with the pip ansible module and
pip-6.1.0+
* Backported support for ansible_winrm_server_cert_validation flag to
disable cert validation on Python 2.7.9+ (and support for other passthru
args to pywinrm transport).
* Backported various updates to user module (prevent accidental OS X group
membership removals, various checkmode fixes).

How do you get it?
--

You can also test this release candidate by cloning the Ansible Github repo
as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v1.9.5-0.1.rc1
$ 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-1.9.5.tar.gz):

$ make sdist

You can then use pip to install the above .tar.gz.

If you discover any errors, please open a Github issue and be sure to
mention you're testing against this release candidate.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFi5hGMYAjrvdSj4By0SvwfrCOFOE1Ba%2BHGcRZPaGBg1Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible networking preview update 2.0.0-0.2 is available

[James Cammarata]

Hi Everyone,

As you undoubtedly heard we released the first version of Ansible 2.0 with
networking support as a technology preview at AnsibleFest London.  In case
you missed the announcement, details can be found here (
http://www.redhat.com/en/about/press-releases/red-hat-brings-devops-network-new-ansible-capabilities)
and here (https://www.ansible.com/network-automation).

Today, we are releasing Ansible 2.0 Network Technology Preview 2 which
addresses several bugs from the original release:

* Fixes bugs when using EOS and NXOS API which would cause some modules to
  generate an exception
* Updates the keys return from JUNOS modules to be consistent with all
  other networking modules.
* Fix for authentication bug when using RSA keys and the CLI transport

The latest release is immediately available at releases.ansible.com.  We
are going to continue to distribute the network technology preview only via
releases.ansible.com until it is merged into Ansible 2.1.

Thanks

James Cammarata
Ansible Project Lead
github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFimAhU%3DYAFyabHa3PCSjsY1bF44Xrg-n-bF%3DqWsGTu%3D0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.1.0 has been released

[James Cammarata]

Hi all, 2.0.1.0 has been released, and is now available.

This release addresses several bugs present in 2.0, such as:

* Improvements to the way no_log filters some output, which may have lead to
  some disclosure of secret variables when using the --diff option.
* Lots of improvements to the synchronize module to bring it back in line
  with 1.9's handling of become/sudo options, among other things.
* Re-implemented retry file support, which was overlooked in the 2.0
release.
  Additionally, retry files are now stored in the same directory as the
  playbook, rather than the home directory (assuming the
retry_files_save_path
  configuration option is not set in your ansible.cfg file).
* Fixes bugs in the implementation of any_errors_fatal. Additionally, we've
  added the ability to set this option on blocks.
* Many unicode fixes.
* Temporary files created by ansible-vault are now "shredded" as an extra
  layer of security.

And many other minor fixes.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

Thanks, and enjoy!

James Cammarata
Ansible Project Lead
github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiRqaZ%2BMaD7oji5yuR-KSPL588sOt_MH5-iJJRNmBVkvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Ansible 2.0.1 RC2 is available for testing

[James Cammarata]

Sorry for not seeing your response before. The release was held up a bit by
AnsibleFest, but we should be getting it out tomorrow.

Thanks!

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Tue, Feb 16, 2016 at 4:36 PM, Slim Slam <slimands...@gmail.com> wrote:

> Any rough estimate on a release date?
>
> J
>
>
> On Monday, February 15, 2016 at 3:12:02 PM UTC-6, James Cammarata wrote:
>>
>> Hi all, we're happy to announce the RC2 release candidate for Ansible
>> 2.0.1 is available and ready for testing. This RC2 continues to address
>> bugs found in the 2.0 release.
>>
>> How do you get it?
>> --
>>
>> The tar.gz of the release can be found here:
>>
>> http://releases.ansible.com/ansible/ansible-2.0.1.0-0.2.rc2.tar.gz
>> SHA256: 4807f8e4b6c70ea1eca6bb3131c19e17d835d2e8884a63d107a842007430285a
>>
>> You can also test against the git repository as follows:
>>
>> $ git clone https://github.com/ansible/ansible.git
>> $ cd ansible
>> $ git checkout v2.0.1.0-0.2.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.1
>> .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
>> Ansible Project Lead
>> github: jimi-c
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/daf3cde9-14b1-40bc-90d1-415c3c14a4d7%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/daf3cde9-14b1-40bc-90d1-415c3c14a4d7%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFhuyuJtvk%2B2-WMdUuJ5eWnGERH2aGibhDgQARso33tPbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.1 RC2 is available for testing

[James Cammarata]

Hi all, we're happy to announce the RC2 release candidate for Ansible 2.0.1
is available and ready for testing. This RC2 continues to address bugs
found in the 2.0 release.

How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.0.1.0-0.2.rc2.tar.gz
SHA256: 4807f8e4b6c70ea1eca6bb3131c19e17d835d2e8884a63d107a842007430285a

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.0.1.0-0.2.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.1
.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
Ansible Project Lead
github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgZjsdZjaNT5BbsUitVCu9PaFybTKFs%3DbuMAxL99sk7%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ansible-project] Ansible 2.0.1 RC1 is available for testing!

[James Cammarata]

Hi all, we're happy to announce the RC1 release candidate for Ansible 2.0.1!

This release candidate includes many bug fixes since the 2.0 release:

* Fixes a major compatibility break in the synchronize module shipped with
  2.0.0.x.  That version of synchronize ran sudo on the controller prior to
  running rsync.  In 1.9.x and previous, sudo was run on the host that rsync
  connected to.  2.0.1 restores the 1.9.x behaviour.
* Additionally, several other problems with where synchronize chose to run
when
  combined with delegate_to were fixed.  In particular, if a playbook
targetted
  localhost and then delegated_to a remote host the prior behavior (in 1.9.x
  and 2.0.0.x) was to copy files between the src and destination
directories on
  the delegated host.  This has now been fixed to copy between localhost and
  the delegated host.
* Fix a regression where synchronize was unable to deal with unicode paths.
* Fix a regression where synchronize deals with inventory hosts that use
  localhost but with an alternate port.
* Fixes a regression where the retry files feature was not implemented.
* Fixes a regression where the any_errors_fatal option was implemented in
2.0
  incorrectly, and also adds a feature where any_errors_fatal can be set at
  the block level.
* Fix tracebacks when playbooks or ansible itself were located in
directories
  with unicode characters.
* Fix bug when sending unicode characters to an external pager for display.
* Fix a bug with squashing loops for special modules (mostly package
managers).
  The optimization was squashing when the loop did not apply to the
selection
  of packages.  This has now been fixed.
* Temp files created when using vault are now "shredded" using the unix
shred
  program which overwrites the file with random data.
* Some fixes to cloudstack modules for case sensitivity
* Fix non-newstyle modules (non-python modules and old-style modules) to
  disabled pipelining.
* Fix fetch module failing even if fail_on_missing is set to False
* Fix for cornercase when local connections, sudo, and raw were used
together.


How do you get it?
--

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

http://releases.ansible.com/ansible/ansible-2.0.1.0-0.1.rc1.tar.gz
SHA256: ab2230f22d742e1379c72a3a59b18779a6aad2b4db69e87e073478028f51b24b

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.0.1.0-0.1.rc1
$ 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.1.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
Ansible Project Lead
twitter: @thejimic github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjy3mHphMPXeWCL1eC%2BRR%2B7D5GxmNqRrV-o4veMSsnzJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Changing actions in case a node fails

[James Cammarata]

Yes, please do.

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Wed, Jan 20, 2016 at 4:19 AM, Dan C <dco...@gmail.com> wrote:

> Hi James,
>
> Yes it seems something is different regarding this on devel branch. But
> either I don't understand what it does or something is not right.
>
> In the current version (2.0.0.0) if I try to use "any_errors_fatal" in a
> block level it fails because this is not an option to be usable on a block.
> With the devel branch this changes. Now I can use this option but it
> doesn't do what I was expecting.
> Now if one of the hosts fails, it make the rest fail and stop executing
> the playbook. But I am not able to have it execute the "rescue" part.
>
>
> - name: deploy
>   hosts: all
>   gather_facts: True
>   tasks:
>   - block:
>   - file: path=/tmp/testfolder1 state=directory
> rescue:
>   - file: path=/tmp/testfolder2 state=directory
> any_errors_fatal: yes
>
> In this example, if I make it fail creating "/tmp/testfolder1", it will
> not be creating "/tmp/testfolder2".
>
> Is this the way it is supposed to work? or should I open an issue on
> github?
>
> Thanks!
>
>
>
>
>> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/7b18bd5b-0bbf-4136-831f-2fa4ca5ef91f%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/7b18bd5b-0bbf-4136-831f-2fa4ca5ef91f%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiiC%3DGCPB1mj%2BobMQHMSYZYFw4j2P07Z9OvFMZW3FFypQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Changing actions in case a node fails

[James Cammarata]

In 2.0.1, we're going to allow the use of any_errors_fatal at the block
level, so you can simply do this:

- block:
  - task1: ..
  - task2: ..
  ...
  - taskN: ..
  rescue:
  - undo_taskN: ..
  ...
  - undo_task2: ..
  - undo_task1: ..
  any_errors_fatal: yes

However, there is currently a bug in 2.0.0.x where any_errors_fatal is not
working as stated in the documentation, so you'll have to wait until we get
2.0.1 out to do this.


James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Tue, Jan 19, 2016 at 4:33 AM, Dan C <dco...@gmail.com> wrote:

> Hi there,
>
> I've been looking arround trying to find a way, with no luck.
>
> When running a playbook against multiple nodes (say 5), and one of them
> fail a task (or block), I would like the other 4 nodes to run different
> tasks than the ones they would run if non of the nodes fail.
>
> Is there any way to signal those nodes or to send them a variable which I
> could use to choose the actions to be taken?
>
> The case of use is that if something fails in any host, I would like to
> "undo" what I have already done...
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/2d3725bd-941a-440f-8d86-b85b8aa7f8c4%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/2d3725bd-941a-440f-8d86-b85b8aa7f8c4%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFjr6YgWG7-k86uqZMb7b37frv%3DxiCzX4sESVfAX%3DFNKnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Re: Included yml task fails

[James Cammarata]

Hi Glenn, could you please open an issue on Github so we can keep track of
this?

Thanks!

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Fri, Jan 15, 2016 at 8:26 AM, Glenn Barnard <barnardgl...@gmail.com>
wrote:

> The underlying problem is this line in the include playbook:
>
>  body: '{ "username" : "{{ username }}", "password" : "{{ password }}"
> }'
>
> If I hardcode the username and password it works. So, this looks like an
> issue with uri, or I've not formatted this correctly.
>
> Suggestions anyone?
>
> On Monday, January 11, 2016 at 3:32:28 PM UTC-5, Glenn Barnard wrote:
>
>> Am using a current copy of Ansible and am in learning stage by writing
>> playbooks that call Ansible's API's via the uri module. Am getting an error
>> from the included yml that is trying to authenticate the user. Note that
>> it's working fine when I put the task into the main yml. The error is a
>> stack trace (below) followed with
>>
>>TypeError: unhashable type
>>
>> Here's the main yml:
>>
>> ---
>> - name: Connect to Ansible API
>>   hosts: localhost
>>   connection: local
>>   gather_facts: no
>>   tasks:
>>   - include: authenticate.yml
>>   url="10.0.0.4"
>>   username=""
>>   password="<password"
>>
>>   - debug: msg='{{ authentication.json }}'
>>
>>   - uri:
>>   url:  https://10.0.0.4/api/v1/users/
>>   method: GET
>>   HEADER_Authorization: TOKEN {{ authentication.json.token }}
>>   validate_certs: no
>>   return_content: yes
>>
>>
>> Here's the included yml:
>>
>> ---
>>
>>   - debug: msg="Connecting to Ansible host with {{ username }}/{{
>> password }}"
>>
>>   - name: Connect to ansible with creds provided
>> uri:
>>   url: https://{{ url }}/api/v1/authtoken/
>>   method: POST
>>   HEADER_Content-Type: application/json
>>   body: '{ "username" : "{{ username }}", "password" : "{{ password
>> }}" }'
>>   validate_certs: no
>>   return_content: yes
>> register: authentication
>>
>>
>> The stack trace is:
>>
>> TASK: [Connect to ansible with creds provided]
>> 
>> failed: [localhost] => {"failed": true, "parsed": false}
>> Traceback (most recent call last):
>>   File
>> "/home/gbarnard/.ansible/tmp/ansible-tmp-1452538099.69-278641758230235/uri",
>> line 2081, in 
>> main()
>>   File
>> "/home/gbarnard/.ansible/tmp/ansible-tmp-1452538099.69-278641758230235/uri",
>> line 416, in main
>> resp, content, dest = uri(module, url, dest, user, password, body,
>> method, dict_headers, redirects, socket_timeut, validate_certs)
>>   File
>> "/home/gbarnard/.ansible/tmp/ansible-tmp-1452538099.69-278641758230235/uri",
>> line 312, in uri
>> resp, content = h.request(url, method=method, body=body,
>> headers=headers)
>>   File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line
>> 1605, in request
>> (response, content) = self._request(conn, authority, uri,
>> request_uri, method, body, headers, redirections, cacekey)
>>   File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line
>> 1353, in _request
>> (response, content) = self._conn_request(conn, request_uri, method,
>> body, headers)
>>   File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line
>> 1290, in _conn_request
>> conn.request(method, request_uri, body, headers)
>>   File "/usr/lib64/python2.7/httplib.py", line 979, in request
>> self._send_request(method, url, body, headers)
>>   File "/usr/lib64/python2.7/httplib.py", line 1013, in _send_request
>> self.endheaders(body)
>>   File "/usr/lib64/python2.7/httplib.py", line 975, in endheaders
>> self._send_output(message_body)
>>   File "/usr/lib64/python2.7/httplib.py", line 839, in _send_output
>> self.send(message_body)
>>   File "/usr/lib64/python2.7/httplib.py", line 811, in send
>> self.sock.sendall(data)
>>   File "/usr/lib64/python2.7/ssl.py", line 723, in sendall
>> v = self.send(data[count:])
>> TypeError: unhashable type
>>
>>
>> FATAL: all hosts have already failed -- aborting
>>
>> --
> You received this message 

[ansible-project] Ansible 2.0.0.2 has been pushed

[James Cammarata]

Hi all, we've just pushed the release of Ansible 2.0.0.2 to address two
issues:

* A traceback for Debian/Ubuntu package users, caused when
python-cryptography is installed but python-setuptools is not present. This
is a packaging fix, where we're adding python-setuptools as a requirement
on the Ansible package.
* A small callback issue, where Tower users would see a warning message
when using 2.0. Users on versions of Tower which support Ansible 2.0 can
upgrade to this version to get rid of the warning message.

As always, this update is available via PyPi and releases.ansible.com now,
and packages for distros will be available as soon as possible.

Thanks!

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFired%2BJHhGsVGwfU-rvdAnmvtG4H4H3JgSDPRp8tBc-Cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] ansible 2.0: limit not working as intended ?

[James Cammarata]

Are you seeing this just with --list-hosts or are you seeing it when
running a playbook too?

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Wed, Jan 13, 2016 at 6:56 AM, Mike Christofilopoulos <mhris...@gmail.com>
wrote:

> im creating my hosts file with
>
> for f in $(seq 1 10); do echo "host$f" >> hosts; done
>
> and then try to list hosts with
>
>
> ansible all -i hosts --limit ~host1 --list-hosts
>
> with this result
>
>   hosts (10):
> host1
> host2
> host3
> host4
> host5
> host6
> host7
> host8
> host9
> host10
>
>
> Also non regex limit reutnrs
>
> ansible all -i hosts --limit host4 --list-hosts
>   hosts (10):
> host1
> host2
> host3
> host4
> host5
> host6
> host7
> host8
> host9
> host10
>
>
> I've tried googling but nothing came up. Has there been any changes ?
>
> ansible 2.0.0.0
>   config file = /etc/ansible/ansible.cfg
>   configured module search path = /usr/share/ansible
>
> and i've installed itwith `pip install --user ansible --upgrade`.
>
>
> Cheers,
> Mike
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/81a1731f-957c-48ed-8aa8-19aec8820926%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/81a1731f-957c-48ed-8aa8-19aec8820926%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgq%2Bb-a-Ub80rTy-HWrCemKKXC_YCGcsGvrAFYrwOk5BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.0 upgrade questions

[James Cammarata]

The first message is for this:

- some_module:
args: "{{some_var}}"

This is, in our opinion, very unsafe - especially when that variable may
come from something like a fact. It has not been disabled, but will be
removed after 2 major versions.

I was unaware of any feature where we silently converted Windows line
endings to POSIX-compliant versions, but you can open an issue in Github
for this.

Finally, this may be an oversight, or a bug in which the deprecation
message for bare variables in loops is not being triggered correctly. This
is fairly minor, but we can look into that as well.

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Tue, Jan 12, 2016 at 5:16 PM, Jacob Weber <weberja...@gmail.com> wrote:

> I'm trying my playbooks with Ansible 2.0, and ran into a few minor issues:
>
> - The Ansible upgrade guide says "Using variables for task parameters is
> unsafe and will be removed in a future version." What does this mean
> exactly? I use variables in task parameters all the time -- this seems
> fundamental to Ansible. Can you clarify this? Is it only when you define
> variables and use them in the same task, like in the example?
>
> - When my source and destination boxes are Linux, and I deployed a
> template with Windows line endings, they used to be converted to Unix line
> endings (in Ansible 1.9). Now the Windows line endings are preserved, but I
> didn't see this in the changelog.
>
> - The upgrade guide says I should receive a deprecation warning in this
> case: "Bare variables in with_ loops should instead use the “{{var}}”
> syntax, which helps eliminate ambiguity." But I'm not getting that warning
> for things like "with_items: some_variable".
>
> Thanks,
>
> Jacob
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFiOVqia6MoSth1Kj4eWFo%3DepK7CW5R%2BVmj4qr2NLcficA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] Ansible 2.0 upgrade questions

[James Cammarata]

It should be specifically related to args.

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Wed, Jan 13, 2016 at 11:23 AM, Tim <caphrim...@gmail.com> wrote:

> Is this specifically related to the args parameter? Or all variable
> content to tasks?
>
> -tim
> On Jan 13, 2016 5:02 AM, "James Cammarata" <jcammar...@ansible.com> wrote:
>
>> The first message is for this:
>>
>> - some_module:
>> args: "{{some_var}}"
>>
>> This is, in our opinion, very unsafe - especially when that variable may
>> come from something like a fact. It has not been disabled, but will be
>> removed after 2 major versions.
>>
>> I was unaware of any feature where we silently converted Windows line
>> endings to POSIX-compliant versions, but you can open an issue in Github
>> for this.
>>
>> Finally, this may be an oversight, or a bug in which the deprecation
>> message for bare variables in loops is not being triggered correctly. This
>> is fairly minor, but we can look into that as well.
>>
>> James Cammarata
>> Director, Ansible Core Engineering
>> github: jimi-c
>>
>> On Tue, Jan 12, 2016 at 5:16 PM, Jacob Weber <weberja...@gmail.com>
>> wrote:
>>
>>> I'm trying my playbooks with Ansible 2.0, and ran into a few minor
>>> issues:
>>>
>>> - The Ansible upgrade guide says "Using variables for task parameters is
>>> unsafe and will be removed in a future version." What does this mean
>>> exactly? I use variables in task parameters all the time -- this seems
>>> fundamental to Ansible. Can you clarify this? Is it only when you define
>>> variables and use them in the same task, like in the example?
>>>
>>> - When my source and destination boxes are Linux, and I deployed a
>>> template with Windows line endings, they used to be converted to Unix line
>>> endings (in Ansible 1.9). Now the Windows line endings are preserved, but I
>>> didn't see this in the changelog.
>>>
>>> - The upgrade guide says I should receive a deprecation warning in this
>>> case: "Bare variables in with_ loops should instead use the “{{var}}”
>>> syntax, which helps eliminate ambiguity." But I'm not getting that warning
>>> for things like "with_items: some_variable".
>>>
>>> Thanks,
>>>
>>> Jacob
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to ansible-project+unsubscr...@googlegroups.com.
>>> To post to this group, send email to ansible-project@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/ansible-project/d1961831-e6d5-4519-8fdf-4cf56240816c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ansible Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ansible-project+unsubscr...@googlegroups.com.
>> To post to this group, send email to ansible-project@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/CAMFyvFiOVqia6MoSth1Kj4eWFo%3DepK7CW5R%2BVmj4qr2NLcficA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/ansible-project/CAMFyvFiOVqia6MoSth1Kj4eWFo%3DepK7CW5R%2BVmj4qr2NLcficA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/CAB0Zv8jWQym1-Y%2BLpcppwnak0Ue4J2wQ-3bUNQC8KgLc0aASig%40mail.gmail.com
> <https://groups.google.com/d/msgid/ansible-project/CAB0Zv8jWQym1-Y%2BLpcppwnak0Ue4J2wQ-3bUNQC8KgLc0aASig%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgYKL8peM3yzPNwE18Poh23SbhR5DhEVELVeFnGp_i8fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] V2 default values not picked up?

[James Cammarata]

That's odd, ansible_ssh_port is still used, it's just an alias to
ansible_port now.

The issue above may be the result of us not adding in all internal
variables to the variable dictionary, so go ahead and open an issue for
this on github (or search to see if someone else has run into this).

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Wed, Jan 13, 2016 at 5:11 AM, Mikael Sandström <orav...@gmail.com> wrote:

> Hi,
>
> I upgraded to 2.0.0.1 (from 1.9.4) this morning and ran one of my
> playbooks to see if things worked and it lit up like a christmas tree. Most
> of that was just warnings (and the fact that ansible_ssh_port is not called
> that any more...), but this thing seems a little more serious (unless I'm
> missing something)
>
> This is on Fedora 23
>
> This works in 1.9.4:
>
> - hosts: localhost
>   connection: local
>   gather_facts: false
>
>
>   tasks:
>
>
>   - name: debug
> debug: msg={{ansible_port|default(22)}}
>
>
>
> PLAY [localhost]
> **
>
>
> TASK: [debug]
> *
> ok: [localhost] => {
> "msg": "22"
> }
>
>
>
> But doesnt work in 2.0.0.1. Its like the default filter is ignored.
>
> TASK [debug]
> ***
> ok: [localhost] => {
> "msg": ""
> }
>
>
> Any ideas?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/53a65287-421a-4bd0-8456-bb8424983944%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/53a65287-421a-4bd0-8456-bb8424983944%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFgoqQd93G_G7wPqcoh8BOoPhAjtKw87BLoV-3MmHBFsvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ansible-project] ansible 2 ping failure

[James Cammarata]

Hrm, looks like there's some garbage in front of the result. Can you open a
github issue for this, with details on the target system included?

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Tue, Jan 12, 2016 at 7:04 PM, Fed <fspad...@gmail.com> wrote:

> Hi Guys,
> I'm having some trouble with the new Ansible 2 when trying to run ping on
> a host that works with 1.9.4.
>
> I'm getting the following:
>
> $ ansible -i test all -m ping -u root -v -c paramiko
>
> Loaded callback minimal of type stdout, v2.0
> <10.10.0.242> ESTABLISH CONNECTION FOR USER: root on PORT 22 TO 10.10.0.242
> <10.10.0.242> EXEC mkdir -p "$( echo
> $HOME/.ansible/tmp/ansible-tmp-1452643119.18-173252181839542 )" && echo "$(
> echo $HOME/.ansible/tmp/ansible-tmp-1452643119.18-173252181839542 )"
> <10.10.0.242> PUT
> /var/folders/1d/nqrbvtz120nb7r2rjqzpvs7mgn/T/tmpjR2gSS TO
> /home/root/.ansible/tmp/ansible-tmp-1452643119.18-173252181839542/ping
> <10.10.0.242> EXEC LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8
> LC_MESSAGES=en_US.UTF-8 /usr/bin/python
> /home/root/.ansible/tmp/ansible-tmp-1452643119.18-173252181839542/ping; rm
> -rf "/home/root/.ansible/tmp/ansible-tmp-1452643119.18-173252181839542/" >
> /dev/null 2>&1
> 10.10.0.242 | FAILED! => {
> "changed": false,
> "failed": true,
> "invocation": {
> "module_name": "ping"
> },
> "module_stderr": "",
> "module_stdout": "\u001b[?1034h{\"invocation\": {\"module_args\":
> {\"data\": null}}, \"changed\": false, \"ping\": \"pong\"}\r\n",
> "msg": "MODULE FAILURE",
> "parsed": false
> }
>
> Previously on 1.9.4 I would get:
>
> $ ansible -i test all -m ping -u root -v -c paramiko
> <10.10.0.242> ESTABLISH CONNECTION FOR USER: root on PORT 22 TO 10.10.0.242
> <10.10.0.242> REMOTE_MODULE ping
> <10.10.0.242> EXEC /bin/sh -c 'mkdir -p
> $HOME/.ansible/tmp/ansible-tmp-1452643204.88-178243528154466 && echo
> $HOME/.ansible/tmp/ansible-tmp-1452643204.88-178243528154466'
> <10.10.0.242> PUT
> /var/folders/1d/nqrbvtz120nb7r2rjqzpvs7mgn/T/tmpqHPWsg TO
> /home/root/.ansible/tmp/ansible-tmp-1452643204.88-178243528154466/ping
> <10.10.0.242> EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8
> /usr/bin/python
> /home/root/.ansible/tmp/ansible-tmp-1452643204.88-178243528154466/ping; rm
> -rf /home/root/.ansible/tmp/ansible-tmp-1452643204.88-178243528154466/
> >/dev/null 2>&1'
> 10.10.0.242 | success >> {
> "changed": false,
> "ping": "pong"
> }
>
> Any idea what the culprit might be?  At first glance the only real
> difference I can see is that the older version had /bin/sh -c in front, but
> that could just be a change in logging.
>
> Cheers
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-project+unsubscr...@googlegroups.com.
> To post to this group, send email to ansible-project@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/cb9a3799-739a-4dc0-98b2-af8a351af94d%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/cb9a3799-739a-4dc0-98b2-af8a351af94d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAMFyvFidiQHGtH%3DtwLwtv%3D%2B4o0iBgbLzkCLnWrEYPzhbUKAU1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.