WINRM Connection always ends up with "STDERR An error occurred while creating the pipeline"

[Jeremie Levy]

Hi

Any task i run is followed by this WINRM error

I am not sure it's an error since the task is done successfully, does someone knows about this?

TASK [Create KIT folder if missing] ****************************************************************************************************************************************************************************************************************************************************************************************

task path: /ansible/scripts/vs2012.yaml:5

Using module file /usr/lib/python2.7/dist-packages/ansible/modules/windows/win_file.ps1

<hasjrwts02> ESTABLISH WINRM CONNECTION FOR USER: ansible on PORT 5986 TO hasjrwts02

creating Kerberos CC at /tmp/tmpnaEGzD

calling kinit for principal ansible

Using module file /usr/lib/python2.7/dist-packages/ansible/modules/windows/win_file.ps1

<hasjrwts01> ESTABLISH WINRM CONNECTION FOR USER: ansible on PORT 5986 TO hasjrwts01

creating Kerberos CC at /tmp/tmpDGNECq

calling kinit for principal ansible

kinit succeeded for principal ansible

<hasjrwts02> WINRM CONNECT: transport=kerberos endpoint=https://hasjrwts02:5986/wsman

kinit succeeded for principal ansible

<hasjrwts01> WINRM CONNECT: transport=kerberos endpoint=https://hasjrwts01:5986/wsman

<hasjrwts02> WINRM OPEN SHELL: F95EFA87-3A14-4F69-AC9B-2BD43120BC93

EXEC (via pipeline wrapper)

<hasjrwts02> WINRM EXEC 'PowerShell' ['-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Unrestricted', '-']

<hasjrwts01> WINRM OPEN SHELL: 421A5D1E-4BC3-42C9-8E02-4B8F28EBDDD7

EXEC (via pipeline wrapper)

<hasjrwts01> WINRM EXEC 'PowerShell' ['-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Unrestricted', '-']

<hasjrwts02> WINRM RESULT u'<Response code 0, out "{"changed":true}\r\n", err "An error occurred wh">'

<hasjrwts02> WINRM STDOUT {"changed":true}

<hasjrwts02> WINRM STDERR An error occurred while creating the pipeline.

    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : RuntimeException

<hasjrwts02> WINRM CLOSE SHELL: F95EFA87-3A14-4F69-AC9B-2BD43120BC93

<hasjrwts01> WINRM RESULT u'<Response code 0, out "{"changed":true}\r\n", err "An error occurred wh">'

<hasjrwts01> WINRM STDOUT {"changed":true}

<hasjrwts01> WINRM STDERR An error occurred while creating the pipeline.

    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : RuntimeException

<hasjrwts01> WINRM CLOSE SHELL: 421A5D1E-4BC3-42C9-8E02-4B8F28EBDDD7

changed: [hasjrwts02] => {

    "changed": true

}

changed: [hasjrwts01] => {

    "changed": true

}

[Jordan Borean]

This is a known issue, technically an error did occur but it does not affect the actual module execution. It was fixed a while ago in the devel branch for the 2.5 release but was only recently back ported to 2.4 and will be available in the 2.4.4 release.

2.5 commit

https://github.com/ansible/ansible/commit/7fce636c2b250aa6ffd7322f03a0c982ecd802e3#diff-9b6915232549a7bcd00b8b8f142b7232

2.4.4 commit

https://github.com/ansible/ansible/commit/e27847eda8d1ea05da8a1b96e085f41134faff94

Thanks

Jordan

[Jeremie Levy]

Thank you Jordan, really appreciate.

I am still not sure it doesn't affect module execution, i have some issues executing win_package. Maybe not related.

[Jordan Borean]

It wouldn't be, those issue seem to be unrelated. In most cases a fatal exception will return a return code that is not 0, in this case rc is still 0.

Thanks

[Jeremie Levy]

You were right, my issue was in my code.

I've "patched" my ansible with the github version and i don't have the error anymore.

Thanks a lot!

On Mon, Jan 29, 2018 at 10:11 AM, Jordan Borean <jbor...@gmail.com> wrote:

It wouldn't be, those issue seem to be unrelated. In most cases a fatal exception will return a return code that is not 0, in this case rc is still 0.

Thanks

--
You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/vypH7W6qvpg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/ae9fa9f9-ce22-417a-9e96-62530356b997%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.