[ansible-project] Re: Weird: Passing variables to roles

2016-06-21 Thread Christoph Wegener
The section about roles in the 'Ansible: Up and Running' book covers this topic quite well. The recommendation in the book is to always prefix var names inside the role with the name of the role, which I believe is for the exact reason of avoiding the scenario that you ran into. On Friday, Ju

Re: [ansible-project] Re: Ansible raw module & Cisco WLC

2016-06-21 Thread Christoph Wegener
pair cannot be used with > Cisco WLC firmware. Or can be? > > 2016-06-14 12:27 GMT+02:00 Christoph Wegener >: > >> Have you tried using RSA key pairs instead of username/password? >> >> On Tuesday, June 14, 2016 at 6:39:43 PM UTC+10, David Vávra wrote: >>

[ansible-project] Re: Ansible raw module & Cisco WLC

2016-06-14 Thread Christoph Wegener
Have you tried using RSA key pairs instead of username/password? On Tuesday, June 14, 2016 at 6:39:43 PM UTC+10, David Vávra wrote: > > Hi, have anyone been succesful with at least logging in to Cisco WLC > device with Ansible? I'm not able to make it work, most probably because of > extra (nons

[ansible-project] Re: urgent, please help: any way to get ansible to work over an unstable connection?

2016-06-11 Thread Christoph Wegener
Step 1: Set up your Ansible Control Machine outside of the country closer to your target machines. Step 2: Learn Tmux or Screen Step 3: Run 'ansible-playbook' in Tmux or Screen on your new Control Machine. On Thursday, May 5, 2016 at 4:21:04 PM UTC+10, nrser wrote: > > this is preventing me fro

[ansible-project] Re: Unusual WinRM connection issue

2016-06-07 Thread Christoph Wegener
If you are referring to cloning a Windows machine without proper sysprep usage then that's very well possible. I remember seeing some WinRM blogs where people had problems due to duplicate SIDs ... not 100% sure though. On Monday, June 6, 2016 at 10:20:21 PM UTC+10, Mike Fennemore wrote: > > I'm

[ansible-project] Re: set_fact for Windows domain login

2016-06-07 Thread Christoph Wegener
I just had a quick look, all log output in ansible is done via python Logger objects. So, I'm not sure if the \\ is actually the representation of you data structure of if the \\ is a result of outputting the data structure via debug. On Tuesday, June 7, 2016 at 11:50:32 PM UTC+10, Chri

[ansible-project] Re: set_fact for Windows domain login

2016-06-07 Thread Christoph Wegener
Just a guess - but wouldn't debug use python pprint and hence why you see \\ in debug? On Tuesday, June 7, 2016 at 11:31:02 PM UTC+10, Mike Fennemore wrote: > > Hi Jon, good call on the \\ , it does now set the fact. However if I run a > debug I see it is now set as domain\\user. > > On Tuesday

[ansible-project] Re: Raw Command to run a UNC Powershell script

2016-05-27 Thread Christoph Wegener
You could, however, have a look at Ansible 2.1 which introduces support for Kerberos Delegation via a new version of pywinrm. The usual Kerberos delegation requirements apply. (Enable accounts for delegation in Active Directory) On Saturday, May 28, 2016 at 12:04:34 AM UTC+10, Christoph

[ansible-project] Re: Raw Command to run a UNC Powershell script

2016-05-27 Thread Christoph Wegener
At the moment, CredSSP is not supported as a WinRM authentication method in Ansible. Without CredSSP support, you will not be able to authenticate to remote CIFS shares like you are trying to do in your example UNC path. On Thursday, March 24, 2016 at 2:10:59 AM UTC+11, Mark Matthews wrote: > >

[ansible-project] Re: Property _ansible_selinux_special_fs in resource xADDomain is not a valid property

2016-05-23 Thread Christoph Wegener
On Monday, May 23, 2016 at 11:05:34 PM UTC+10, Christoph Wegener wrote: > > > > On Monday, May 23, 2016 at 9:16:26 PM UTC+10, Trond Hindenes wrote: >> >> Hmm, might be time for me to update the generator scripts. I'll look into >> it and get back to you! >&

[ansible-project] Re: Property _ansible_selinux_special_fs in resource xADDomain is not a valid property

2016-05-23 Thread Christoph Wegener
On Monday, May 23, 2016 at 9:16:26 PM UTC+10, Trond Hindenes wrote: > > Hmm, might be time for me to update the generator scripts. I'll look into > it and get back to you! > > Dang! Perfect timing. I ran into the internal ansible variable handling issue in win_dsc5 literally just now! (Trying t