-
Notifications
You must be signed in to change notification settings - Fork 23.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected CLIXML in stderr output #67964
Comments
Files identified in the description: If these files are inaccurate, please update the |
cc @jborean93 |
Files identified in the description: If these files are incorrect, please update the |
@P-Hessler Is your script consume a lot of memory? I met the same problem, and turns out that my script consume a lot of memory. |
@actini Glad, you could solve the problem in your case. Unfortunately, my script does not consume a lot of memory. As stated in the issue, this is even reproducible with an empty script. |
I got the same kind of error while using script module, even if tried $ProgressPreference = "SilentlyContinue" and $ErrorActionPreference = "SilentlyContinue", it didn't solved. Then I saw that when I run the script in win_shell module instead of using script module, it worked. I'm aware that the playbook looks bad when I write a long script in win_shell, but I couldn't find any other way to solve the related error. Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1024 also didn't solve.
|
Did someone find a workaround for this error ? |
SUMMARY
Hi,
I'm using ansible v2.9.5 (the problem exists at least since version 2.9.1).
The issue:
Using the script module in order to execute scripts with escalated rights leads to unexpected output in stderr.
In ansible version 2.7.10 the behavior is as expected.
ISSUE TYPE
COMPONENT NAME
script
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Windows Server 2016
64bit
STEPS TO REPRODUCE
Simply execute the following playbook.
File
site.yml
File
SomeScript.ps1
is empty.EXPECTED RESULTS
ACTUAL RESULTS
The task seems to be executed correctly.
I executed with -vvvvvv
The message "Module werden für erstmalige Verwendung vorbereitet." translates to "Modules are prepared for first usage."
The reason for the stderr output seems to be the additional element
inside the 3rd -element.
The text was updated successfully, but these errors were encountered: