Multiple issues with launching well-known good jobs on slave nodes have been occurring intermittently (<50%.) Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:
Jobs failing due to "ERROR: Unexpected exception occurred while performing online-node command. java.net.SocketTimeoutException: Read timed out"
Jobs failing due to "ERROR: (job name) aborted." with no record of any user abort or reason for abort
Jobs failing due to "FATAL: command execution failed java.nio.channels.ClosedChannelException"
This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve the issue.
Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.
These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information.
Please note: My company has recommended I remove the logs which were originally attached to this bug. I can still provide specifics and logs which do not contain system names or IPs upon request.
Multiple issues with launching well-known good jobs on slave nodes have been occurring intermittently (<50%.) Downgrading from Jenkins version 2.164.1 to 2.150.3 unfortunately does not appear to resolve the issue. Specifically:
This was reproduced over the course of multiple days and randomly started about a week ago. No workaround was found for this issue, and a downgrade was unable to resolve the issue.
Notepad documents containing the entirety of each of these errors from our job output have been attached, but if any other logs are needed, please let me know.
These jobs provide a variety of functions, mostly in the way of running simple batch commands, disconnecting the node, then reconnecting only after a ping response fails for a time, then succeeds. The output provided should provide more information.
Originally reported by cdavies, imported from: Unexpected exception occurred while performing online-node command