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

Build cannot be resumed if parallel was used with Kubernetes plugin

    XMLWordPrintable

Details

    • workflow-cps 2.66

    Description

      I have a lot of Pipeline Jobs that are waiting for user input before deploying to production. It is quite normal, that pipelines are in this state for several days.

      After a Jenkins restart (e.g. because of a Jenkins Update) the Pipelines are still in running state, but the user input controls are missing.

      log

      pipeline view

      paused for input
      Paused for input is available, but the controls are missing.

      blue ocean

      Attachments

        1. blue ocean.png
          blue ocean.png
          39 kB
        2. log.png
          log.png
          57 kB
        3. paused for input.png
          paused for input.png
          138 kB
        4. pipeline view.png
          pipeline view.png
          68 kB

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-37998 Warning log "no flow execution found for pipelinejob #1"

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41854 Contextualize a fresh FilePath after an agent reconnection

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53709 Parallel blocks in node blocks cause executors to be persisted outside of the node block

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-63164 Closures in block-scoped steps can reference dead CpsBodyExecutions

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39552 After restart, interrupted pipeline deadlocks waiting for executor

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link workflow-cps #279

          Activity

            Ascending order - Click to sort in descending order
            View 20 older comments
            jglick Jesse Glick added a comment -

            I was hoping that my proposed fix of JENKINS-41854 would solve the symptom in at least some cases, by allowing a PickleDynamicContext to be saved in program.dat rather than the actual FilePath in a DryCapsule. Unfortunately it does not seem to work—something is apparently still trying to rehydrate the bogus pickle—though at least the override of TryRepeatedly.getOwner from FilePathPickle makes the problem a bit more apparent, as the resumed build will repeatedly print

            Still trying to load Looking for path named ‘/home/jenkins/workspace/workaround’ on computer named ‘jenkins-input-repro-48e88ac1-40ab-4d74-9ba2-1f25e728be3c--3h6s8’
            jglick Jesse Glick added a comment - I was hoping that my proposed fix of JENKINS-41854 would solve the symptom in at least some cases, by allowing a PickleDynamicContext to be saved in program.dat rather than the actual FilePath in a DryCapsule . Unfortunately it does not seem to work—something is apparently still trying to rehydrate the bogus pickle—though at least the override of TryRepeatedly.getOwner from FilePathPickle makes the problem a bit more apparent, as the resumed build will repeatedly print Still trying to load Looking for path named ‘/home/jenkins/workspace/workaround’ on computer named ‘jenkins-input-repro-48e88ac1-40ab-4d74-9ba2-1f25e728be3c--3h6s8’
            jglick Jesse Glick added a comment -

            Digging into the program state confirms that all kinds of stuff including the ContainerExecDecorator is still there even after the container step exited. Seems like a bug in ParallelStep.

            jglick Jesse Glick added a comment - Digging into the program state confirms that all kinds of stuff including the ContainerExecDecorator is still there even after the container step exited. Seems like a bug in ParallelStep .
            jglick Jesse Glick added a comment -

            JENKINS-53709 was a similar issue.

            jglick Jesse Glick added a comment - JENKINS-53709 was a similar issue.
            jglick Jesse Glick added a comment -

            Have a fix for the workflow-cps problem, and it seems to correct the symptom as reported here. JENKINS-37998 is still valid, since it could affect other scenarios, but this seems to be the important fix.

            jglick Jesse Glick added a comment - Have a fix for the workflow-cps problem, and it seems to correct the symptom as reported here. JENKINS-37998 is still valid, since it could affect other scenarios, but this seems to be the important fix.
            dnusbaum Devin Nusbaum added a comment -

            A fix for this issue was just released in version 2.66 of Pipeline: Groovy Plugin.

            dnusbaum Devin Nusbaum added a comment - A fix for this issue was just released in version 2.66 of Pipeline: Groovy Plugin.

            People

              jglick Jesse Glick
              dawi Daniel Wilmer
              Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: