v4.9.0-20230111 rundeck-winrm-plugin not able to connect/run commands on Windows computers

[greggreer]

Description

After upgrading from version v4.8.0-20221110 to version 4.9.0-20230111, the rundeck-winrm-plugin (v1.3.3) is not able to connect to Windows servers to run commands. When we attempt to connect, we get an error message similar to the following:

Failed dispatching to node orbcsweb02: com.dtolabs.rundeck.core.CoreException

Execution failed: 1427803 in project Xactimate: [Workflow result: , step failures: {1=NodeDispatchFailure: Failed dispatching to node orbcsweb02: com.dtolabs.rundeck.core.CoreException}, Node failures: {orbcsweb02=[Unknown: com.dtolabs.rundeck.core.CoreException]}, flow control: Continue, status: failed]

This was working correctly under v4.8.0, but after the upgrade, we are not able to connect to our Windows servers.

My Rundeck detail

• Rundeck version: 4.9.0-20230111
• install type: rpm
• OS Name/version: Amazon Linux 2 (4.14.301-224.520.amzn2.x86_64)
• DB Type/version: postgres

To Reproduce

Steps to reproduce the behavior:

1. Login to Rundeck
2. Go to a configured project
3. Click on a job that runs a command on a windows-based server/computer
4. Allow the job to run
5. Click on 'Log Output' to display the log which displays the error

Expected Behavior

Rundeck is able to connect to the server and perform the command(s) specified in the job.

Desktop (please complete the following information):

• OS: Windows, Linux, Mac
• Browser Chrome, Firefox, Microsoft Edge
• Version Windows 10, Mac OS 12/13

Additional Context

The error message produced by this issue does not provide any information as to what the problem may be. I have checked possible issues like not being able to find the keys needed for authentication for the connection. Those keys are available, and in the location that is configured for the Node Executor.

We configure our project settings similar to:

project.winrm-auth-type=basic
project.ssh-authentication=privateKey
project.winrm-protocol=http
project.winrm-timeout=PT360.000S
service.FileCopier.default.provider=stub
project.winrm-connection-timeout=30000
project.description=Project Name
project.ssh-keypath=/var/lib/rundeck/.ssh/id_rsa
resources.source.1.config.includeServerNode=true
resources.source.1.config.format=resourcexml
service.NodeExecutor.default.provider=overthere-winrm
resources.source.1.config.requireFileExists=false
project.name=Project Name
resources.source.1.type=file
project.winrm-password-storage-path=keys/win_keys/admin
resources.source.1.config.file=/var/rundeck/projects/Project Name/etc/resources.xml
project.winrm-locale=en-us

[karma2max]

Upgrade of the rundeck-winrm-plugin to v1.3.8 has not solved the issue

[MarcusCaepio]

Hi all, we can confirm this. We are currently facing the same issue after the update:

Failed dispatching to node xxx: com.dtolabs.rundeck.core.CoreException Execution failed: 13029 in project xxx: 
[Workflow result: , step failures: {1=Dispatch failed on 1 nodes: [xxx: Unknown: com.dtolabs.rundeck.core.CoreException]}, 
Node failures: {xxx=[Unknown: com.dtolabs.rundeck.core.CoreException]}, status: failed]

[MarcusCaepio]

Addtitional Info: Job is working again without problems after downgrading to 4.8

[karma2max]

Hi all,

same error with Rundeck 4.10

[2023-02-14T09:40:34,567] ERROR services.PluginService - NodeExecutor: configuration was not valid for plugin 'overthere-winrm': hostnameVerify: Invalid value: BROWSER_COMPATIBLE certTrust: Invalid value: STRICT

[2023-02-14T09:40:34,925] ERROR services.ExecutionUtilService - Execution failed: 26106 in project Windows-Server: [Workflow result: , step failures: {1=Dispatch failed on 1 nodes: [xxx.: Unknown: com.dtolabs.rundeck.core.CoreException]}, Node failures: {xxx=[Unknown: com.dtolabs.rundeck.core.CoreException]}, status: failed]