[ansible-project] Ansible 2.5.13, 2.6.10, and 2.7.4 are available

Hi all, Ansible 2.5.13, 2.6.10, and 2.7.4 were released today. These releases only include a fix for a packaging oversight that caused Windows targets to fail execution. The new releases are available via the usual installation methods on PyPI, https://releases.ansible.com/ansible/, and on Gi

[ansible-project] Ansible 2.5.12, 2.6.9, and 2.7.3 are available

Hi all, Ansible 2.5.12, 2.6.9, and 2.7.3 were released today. These releases include a fix for a reported security vulnerability CVE-2018-16859 (https://nvd.nist.gov/vuln/detail/CVE-2018-16859), as well as other small bugfixes. Special thanks to community member Igor Turovsky for responsibly r

[ansible-project] Ansible 2.5.11 and 2.6.7 are available

Hi all, Ansible 2.5.11 and 2.6.7 were released today. These releases only fix reported security vulnerability CVE-2018-16837 (https://nvd.nist.gov/vuln/detail/CVE-2018-16837). The fix protects the user module from potentially disclosing the passphrase used for ssh-keygen when generating a new

[ansible-project] Ansible 2.5.10 is available

Hi all- we're happy to announce that the general release of Ansible 2.5.10 is now available! How do you get it? -- $ pip install ansible==2.5.10 --user The tar.gz of the release can be found here: https://releases.ansible.co

[ansible-project] Ansible 2.5.9 is available

Hi all- we're happy to announce that the general release of Ansible 2.5.9 is now available! How do you get it? -- $ pip install ansible==2.5.9 --user The tar.gz of the release can be found here: https://releases.ansible.com/

[ansible-project] Ansible 2.5.8 is available

Hi all- we're happy to announce that the general release of Ansible 2.5.8 is now available! How do you get it? -- $ pip install ansible==2.5.8 --user The tar.gz of the release can be found here: https://releases.ansible.com/

[ansible-project] Ansible 2.5.3 is available

Hi all- we're happy to announce that the general release of Ansible 2.5.3 is now available! How do you get it? -- $ pip install ansible==2.5.3 --user The tar.gz of the release can be found here: https://releases.ansible.com/

[ansible-project] Ansible 2.5.2 is available

Ansible 2.5.2 is available Hi all- we're happy to announce that the general release of Ansible 2.5.2 is now available! This release was fast-tracked to fix a regression around setting facts inside loops that was hitting a large number of users. More details: https://github.com/ansible/ansible

[ansible-project] Ansible 2.5.1 is available

Hi all- we're happy to announce that the general release of Ansible 2.5.1 is now available! How do you get it? -- $ pip install ansible==2.5.1 --user The tar.gz of the release can be found here: https://releases.ansible.com/

[ansible-project] Ansible 2.5.0 Final is available

Hi all- we're happy to announce that the general release of Ansible 2.5.0 is now available! How do you get it? -- $ pip install ansible==2.5.0 --user The tar.gz of the release can be found here: https://releases.ansible.com/

[ansible-project] Ansible 2.5.0 Release Candidate 3 is available

Hi all- we're happy to announce that Release Candidate 3 of Ansible 2.5.0 is now available! How do you get it? -- All Ansible pre-releases in the 2.5 series will be published to PyPI. This is probably the easiest way for most

[ansible-project] Ansible 2.5.0 Release Candidate 2 is available

Hi all- we're happy to announce that Release Candidate 2 of Ansible 2.5.0 is now available! How do you get it? -- All Ansible pre-releases in the 2.5 series will be published to PyPI. This is probably the easiest way for most

[ansible-project] Re: kerberos: Bad HTTP response returned from server. Code 400

Yep, the non-default encryption setting is almost certainly the issue. Can you file a bug on https://github.com/02strich/pykerberos? No promises that we'll get to it, but I have a couple ideas as to what might be causing it. I *think* the fix could be pretty simple (there's a code path in there

Re: [ansible-project] Ansible 2.5.0 Release Candidate 1 is available

Tag support in 2.5.0 is passing all the integration tests, so I'd be surprised if it's not working, but If you've got a reproducible issue, please file it on Github. On Saturday, February 24, 2018 at 6:34:41 AM UTC-8, Michael Ströder wrote: > > wrote: > > Hi all- we're happy to announce that R

[ansible-project] Re: kerberos: Bad HTTP response returned from server. Code 400

On a related note: maybe try just tweaking the existing setup to use `ansible_winrm_message_encryption=never` on your Windows host(s) in the inventory or via `-e` to prove if it's related to the new message encryption support. You've clearly been running unencrypted in the past- we'll leave the

[ansible-project] Ansible 2.5.0 Release Candidate 1 is available

Hi all- we're happy to announce that Release Candidate 1 of Ansible 2.5.0 is now available! How do you get it? -- All Ansible pre-releases in the 2.5 series will be published to PyPI. This is probably the easiest way for most

[ansible-project] Re: Ansible and PowerShell 6 (Core)

Powershell 6 on Windows is not really a replacement for Powershell 5; it's kind of a long-term goal to try and make most things work under it, but *lots* of stuff is still broken and unsupported by Microsoft. Windows Nano Server as a standalone manageable OS was our primary driver for trying to

[ansible-project] Re: Ansible 2.5.0 Alpha 1 is available

Sorry about that- some docs reorgs in devel moved that right after we sent the release announcement, and the redirects aren't in place yet. New location is https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.5.html . -Matt On Wednesday, February 14, 2018 at 5:59:20 AM UTC-8,

[ansible-project] Re: Ansible and PowerShell 6 (Core)

We've done some experimentation with it, and it's possible, but it required "if pwsh do X, else do Y" in several of the core connection methods (around hash calculation, etc), as some .NET things have moved around since .NET 4.0 on the oldest platforms we support. Just out of curiosity: why is

[ansible-project] Ansible 2.5.0 Alpha 1 is available

Hi all! We're happy to announce that Alpha 1 for 2.5.0 is now available. Note that while the core engine is feature complete, community module freeze is next week, so new modules and features will appear in the next pre-release. How do you get it? --

[ansible-project] Re: ANSIBLE_KEEP_REMOTE_FILES location on windows target?

The target dir is also visible if you run with -vvv or higher when we're not pipelining, eg: <192.168.33.51> PUT "/tmp/tmpflvOc3" TO "C:\Users\vagrant\AppData\Local\Temp\ansible-tmp-1513649854.81-279137826312538\win_ping.ps1" On Wednesday, December 13, 2017 at 2:19:54 AM UTC-8, Gareth Stockdale

[ansible-project] Windows folks: help test the new pywinrm beta!

We're pleased to announce the release of pywinrm 0.3.0 beta 1, and hoping our friends that manage Windows with Ansible will put it through its paces... The marquee feature on this release enables HTTP message encryption on NTLM, Kerberos, and CredSSP (in conjunction with updates to several othe

[ansible-project] Re: Baremetal provisioning on Windows Hyper-V

Now that we're shipping win_dsc in the box (2.4/devel), you might also want to have a look at the xHyperV DSC module... On Thursday, July 6, 2017 at 2:07:28 PM UTC-7, David Armstrong wrote: > > Add me as a +1 for Hyper-V / SCVMM support. > > We are a mixed VMware and Hyper-V shop. We looked at v

[ansible-project] Re: wait_for a windows file

We've got a win_wait_for module on the roadmap for 2.4. Meantime, a win_shell task with a one-liner while loop using Test-Path and Start-Sleep should do the trick. -Matt On Thursday, June 8, 2017 at 8:48:18 AM UTC-7, Paul Farrington wrote: > > Stavros, did you ever get this resolved as i have t

[ansible-project] Re: Windows Kerberos Issues

The domain status of the Ansible controller shouldn't matter. If DNS is working, the typical remaining causes of that error are not using the FQDN of the target host in your Ansible inventory, or that the host's HTTP SPN has been reassigned to another user. Also, if you don't absolutely need to