Details
-
Type:
New Feature
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: workflow-durable-task-step-plugin
-
Labels:None
-
Environment:Jenkins ver. 2.53
Pipeline job /
Pipeline: Nodes and Processes plugins : ver. 2.10
-
Similar Issues:
Description
Preconditions
Jenkins pipeline job is configured to run parallel actions in different docker swarm nodes.
Procedure
- Run job
- Force disconnect of a node running a part of this job
Actual outcome
Job will never terminate. The pipeline part will remain stuck in:
Cannot contact swarm-xxxxxxxx: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
The exception is catched by workflow-durable-task-step-plugin and used to display the log above.
Expected outcome
The pipeline part execution should generate an exception that can be catched.
This will can allow implementing a retry strategy in Pipeline job.
Attachments
Issue Links
- duplicates
-
-
- Open
-
- relates to
-
JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node
-
- Closed
-
Activity
Aymen Bouaziz
created issue -
Aymen Bouaziz
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
*Preconditions* Jenkins pipeline job is configured to run parallel actions in different docker swarm nodes. *Procedure* # Run job # Force disconnect of a node running a part of this job *Actual outcome* Job will never terminate. The pipeline part will remain stuck in: Cannot contact swarm-xxxxxxxx: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException The exception catched by workflow-durable-task-step-plugin and used to display the log above. *Expected outcome* The pipeline part execution should generate an exception that can be catched. This will can allow implementing a retry strategy in Pipeline job. |
*Preconditions* Jenkins pipeline job is configured to run parallel actions in different docker swarm nodes. *Procedure* # Run job # Force disconnect of a node running a part of this job *Actual outcome* Job will never terminate. The pipeline part will remain stuck in: {noformat} Cannot contact swarm-xxxxxxxx: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException{noformat} The exception is catched by workflow-durable-task-step-plugin and used to display the log above. *Expected outcome* The pipeline part execution should generate an exception that can be catched. This will can allow implementing a retry strategy in Pipeline job. |
| Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
| Link |
This issue relates to |
Jesse Glick should this get more attention? there are a number of tickets and questions turning up online as ephemeral nodes are becoming way more common. GKE in particular makes its very cheap and easy.
Michael McCallum
added a comment - Jesse Glick should this get more attention? there are a number of tickets and questions turning up online as ephemeral nodes are becoming way more common. GKE in particular makes its very cheap and easy. | Link | This issue duplicates JENKINS-49707 [ JENKINS-49707 ] |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
As with
JENKINS-36013, currently the model is that a node may go offline and later be reconnected, in which case the step will quietly resume printing output and exit normally. For Swarm or other cloud-like node schemes, a disconnection may be followed by an actual permanent removal of the node definition, in which case it would be desirable for the step to abort.