Well, apparently there's *some* kind of python glue installed. I did kinit to acquire a ticket for the appropriate user, and I was able to get it to work.
There still needs to be a switch. I don't want to muck about with kinit every time I want to run playbooks. On Monday, March 30, 2015 at 2:26:23 PM UTC-7, Peter Loron wrote: > > As far as I know, I do not have pykerberos installed. If I start the > default python and do "import kerberos", it fails. > > Regardless, there should be an option to force the connection type. > > On Sunday, March 29, 2015 at 2:56:26 PM UTC-7, J Hawkesworth wrote: >> >> If I recall, if you have pykerberos installed, winrm will attempt >> kerberos connection. >> >> I guess your options are to remove pykerberos or use knit to acquire a >> kerberos ticket and connect as a domain user. >> >> Hope that helps. >> >> Jon > > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/af652d85-9d86-4c1c-9e09-24a23d17da7f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
