Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43607

Jenkins pipeline not aborted when the machine running docker container goes offline

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • 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

      1. Run job
      2. 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

            Activity

            aymen_parrot Aymen Bouaziz created issue -
            aymen_parrot 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.
            jglick Jesse Glick made changes -
            Issue Type Bug [ 1 ] New Feature [ 2 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-36013 [ JENKINS-36013 ]
            jglick Jesse Glick made changes -
            Link This issue duplicates JENKINS-49707 [ JENKINS-49707 ]
            jglick Jesse Glick made changes -
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              aymen_parrot Aymen Bouaziz
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: