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

Warning log "no flow execution found for pipelinejob #1"

    XMLWordPrintable

Details

    Description

      Hi,

      When testing pipeline's durability, I tried killing a sample running pipeline to see how it behaves.

      After killing forcefully the server, though there seems to me no problem from an UI standpoint, I saw the following log I thought I would report:

      WARNING: no flow execution found for pipelinejob #1

      How to reproduce:

      • run a brand new 2.7.3
      • install suggested plugins
      • create a pipeline job with the following script:
      // input normally returns a map, BUT returns directly the value if there's only one param
def loopCount = input message: 'Continue? If so, how many iterations?', parameters: [string(defaultValue: '', description: '', name: 'loopCount')]
assert loopCount.isNumber() : "oh noes, beware JENKINS-34488"

stage "looping"

for ( int i=0 ; i< loopCount.toInteger() ; i++) {
    echo "$i"
    sleep 5
}
      • Run the pipeline
      • Answer the input, and put 10 for example
      • Kill -9 the master
      • Restart it
      • Refresh the console
      • See the pipeline finish correctly
      • Go back to the job page
      • See the message: WARNING: no flow execution found for pipelinejob #1
      • (sometimes seems to require two kills to trigger that, still trying to refine the reproduction case)

      WDYT?

      Leaving as minor because as said above, the durability seems still to be working since the pipeline always does restart from where it left in my tests.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-41791 Build cannot be resumed if parallel was used with Kubernetes plugin

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-44855 input leaves build hanging - input.InputAction loadExecutions no flow execution found

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-63820 No flow execution for input in lock block after restart

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

          Web Link CloudBees Internal CD-48

          Web Link PR 3

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            reinholdfuereder Reinhold Füreder added a comment -

            Since massively upgrading Jenkins (core 2.270 => 2.283; 77 plugins!) I stumbled again over this warning message log spam:

            • it accounts for 16488 of 16865 log lines!
              • (I am pretty sure it has nothing to do with the upgrade, because this log spam was there ever since; it is just more massive, but maybe due to our behaviour: see below)

            Admittedly the single pipeline with this "push button deployment (input step wrapped into timeout)" is under heavy development, so I guess that 2-4 colleagues have Jenkins UI for this pipeline opened in 1..N browser windows/tabs...
            Potentially also interesting is, that I am using these non-official API calls (cf. "@Restricted(NoExternalUse.class)" annotation) to allow nice UI for skipped stages in scripted pipelines (like for declarative ones) based on https://github.com/comquent/imperative-when (see https://issues.jenkins-ci.org/browse/JENKINS-47286).

            Thanks for any progress/help to reduce or ideally "just" avoid this log spam

            reinholdfuereder Reinhold Füreder added a comment - Since massively upgrading Jenkins (core 2.270 => 2.283; 77 plugins!) I stumbled again over this warning message log spam: it accounts for 16488 of 16865 log lines! (I am pretty sure it has nothing to do with the upgrade, because this log spam was there ever since; it is just more massive, but maybe due to our behaviour: see below) Admittedly the single pipeline with this " push button deployment (input step wrapped into timeout) " is under heavy development, so I guess that 2-4 colleagues have Jenkins UI for this pipeline opened in 1..N browser windows/tabs... Potentially also interesting is, that I am using these non-official API calls (cf. "@Restricted(NoExternalUse.class)" annotation) to allow nice UI for skipped stages in scripted pipelines (like for declarative ones) based on https://github.com/comquent/imperative-when (see https://issues.jenkins-ci.org/browse/JENKINS-47286 ). Thanks for any progress/help to reduce or ideally "just" avoid this log spam
            tamerlaha ipleten added a comment -

            Yes we have the same problem. And seems it is related to pipelines with input step as reinholdfuereder mentioned.

            tamerlaha ipleten added a comment - Yes we have the same problem. And seems it is related to pipelines with input step as reinholdfuereder mentioned.
            aoutler Adam Outler added a comment -

            This affects me too.  I'm accumulating log spam at a rate of 4messages per minute per job with input step, at the start of each minute.   My total rate is approximately 12 log messages per second but these 12 messages all occur within a second. 

            2021-10-19 09:24:46.818+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19
2021-10-19 09:24:46.818+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19
2021-10-19 09:24:46.819+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25
2021-10-19 09:24:46.820+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25
2021-10-19 09:24:46.824+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4
2021-10-19 09:24:46.824+0000 [id=124666]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4
2021-10-19 09:24:46.858+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19
2021-10-19 09:24:46.859+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19
2021-10-19 09:24:46.863+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25
2021-10-19 09:24:46.864+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25
2021-10-19 09:24:46.867+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4
2021-10-19 09:24:46.867+0000 [id=124920]	WARNING	o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4

            There's a ton of log spam for this issue. 

            aoutler Adam Outler added a comment - This affects me too.  I'm accumulating log spam at a rate of 4messages per minute per job with input step, at the start of each minute.   My total rate is approximately 12 log messages per second but these 12 messages all occur within a second.  2021-10-19 09:24:46.818+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19 2021-10-19 09:24:46.818+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19 2021-10-19 09:24:46.819+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25 2021-10-19 09:24:46.820+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25 2021-10-19 09:24:46.824+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4 2021-10-19 09:24:46.824+0000 [id=124666] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4 2021-10-19 09:24:46.858+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19 2021-10-19 09:24:46.859+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB #19 2021-10-19 09:24:46.863+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25 2021-10-19 09:24:46.864+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB2 #25 2021-10-19 09:24:46.867+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4 2021-10-19 09:24:46.867+0000 [id=124920] WARNING o.j.p.w.s.s.input.InputAction#loadExecutions: no flow execution found for MYJOB3 #4 There's a ton of log spam for this issue. 
            reinholdfuereder Reinhold Füreder added a comment - - edited

            Maybe JENKINS-44855 and JENKINS-63820 are even duplicates?

            reinholdfuereder Reinhold Füreder added a comment - - edited Maybe JENKINS-44855 and JENKINS-63820 are even duplicates?
            reinholdfuereder Reinhold Füreder added a comment -

            (It seems to be independent of wrapping the input into timeout step though.)

            And it is really causing a lot of log spam, because it comes again and again (for all the old builds until they are discarded)
            => I would be extremely happy if this would be fixed PRAY

            reinholdfuereder Reinhold Füreder added a comment - (It seems to be independent of wrapping the input into timeout step though.) And it is really causing a lot of log spam, because it comes again and again (for all the old builds until they are discarded) => I would be extremely happy if this would be fixed PRAY

            People

              Unassigned Unassigned
              batmat Baptiste Mathus
              Votes:
              8 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated: