[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

2018-02-28 Thread Jordan Borean
No worries, when you run the windows-integration tests it will load the inventory file I mentioned. You can't use Python modules on Windows hosts as it will either fail with a send input error or the one you see with ANSIBALLZ. Glad you got it working though, good luck with the testing.

[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

2018-02-28 Thread Guillem Sola
Your help is really appreciated and it's helping me understand better how the testing framework works. It ended up being my fault (what else) I confused the include tests tasks and it was doing the setup with the copy instead of win_copy command. Maybe the test runner is forcing everything to

[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

2018-02-28 Thread Guillem Sola
Your help is really appreciated and it's helping me understand better how the testing framework works. It ended up being my fault (what else) I confused the include tests tasks and it was doing the setup with the copy instead of win_copy command. Thanks On Wednesday, February 28, 2018 at

[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

2018-02-28 Thread Guillem Sola
The win_xml module lives in a forked repo and has been pending to be merged for some months https://github.com/ansible/ansible/pull/26404. I'm using it in my deployments and I was considering continuing the original work to see if it can be merged. It is a PS module but with what you have

[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

2018-02-28 Thread Toshio Kuratomi
On Tuesday, February 27, 2018 at 11:16:28 PM UTC-8, Guillem Sola wrote: > > Hi, > > I'm trying to run some integration tests from ubuntu against a windows10 > host with > > ./ansible-test windows-integration -v win_xml --allow-destructive > > Test tasks starts but it complains > > fatal: