Why do you put that in just out of interest Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: [email protected] <[email protected]> on behalf of Ryan Nix <[email protected]> Sent: Tuesday, January 12, 2021 1:10:47 PM To: Ansible Project <[email protected]> Subject: Re: [ansible-project] Windows module error with ansible.legacy.setup PowerShell -NoProfile -NonInteractive?
Sorry, you're right, I should have posted what I changed. I added these lines from the example here. https://docs.ansible.com/ansible/latest/user_guide/windows_setup.html#installing-win32-openssh - name: set the default shell to PowerShell win_regedit: path: HKLM:\SOFTWARE\OpenSSH name: DefaultShell data: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe type: string state: present It worked fine when I ran it after the addition, but the subsequent runs of my playbook turned up the error. I've even tried removing the "set the default shell to Powershell" snippet and it's still turning up this vexing error. So you're right, it's like this Powershell example did something that is breaking subsequent runs. On Monday, January 11, 2021 at 4:49:05 PM UTC-6 Antony Stone wrote: On Monday 11 January 2021 at 23:16:28, Ryan Nix wrote: > Hello, > > I had my playbook working perfectly until I made what I thought was a small > change! It would probably help if you told us exactly what that change was - show us the old version and the new one (or, at least, the bits that are different). > Ansible keeps telling me there is a problem with line 1 but I'm having a > hard time interpreting what the error means. Almost seems like VS Code did > something? > > Error: > > "At line:1 char:26\r\n+ chcp.com<http://chcp.com> 65001 >nul 2>&1 && > PowerShell -NoProfile - > NonInteractive -Ex ...\r\n+ ~~\r\nThe token '&&' is not a valid statement > separator in this version.\r\n" That to me looks more like a complaint about the powershell script you're using to call ansible than it does about the ansible playbook itself (however on the other hand I know nothing whatever about powershell so I could be completely wrong). I simply don't see an instance of '&&' in your playbook, so the error can't be talking about that. Antony. -- All generalisations are inaccurate. Please reply to the list; please *don't* CC me. -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/89476fe1-6c90-470a-ba9b-2e58f6b303een%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/89476fe1-6c90-470a-ba9b-2e58f6b303een%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/SY4PR01MB5770F11FE26734E56DEE822CADAA0%40SY4PR01MB5770.ausprd01.prod.outlook.com.
