• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: datadog-plugin, workflow-api-plugin
• Labels:

  None
• Environment:

  jenkins-version - 2.263.1
  workflow-job - 2.40
  workflow-api - 2.40
  Datadog-plugin - 2.60.1

1. 

   stuck_build_queue.png

   42 kB

   2021-01-22 08:37

[JENKINS-64688] Upgrading Datadog plugin to 2.6.0 breaks Jenkins

Ajay Kumar created issue - 2021-01-22 08:41

Ajay Kumar made changes - 2021-01-22 09:56

Description	Original: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-api plugin to be at least at 2.40*  After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue. We see multiple of these in our logs, which is similar to JENKINS-52362 {code:java} //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}	New: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40*  After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.  We see multiple of these in our logs, which is similar to JENKINS-52362 {code:java} //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}
Environment	Original: jenkins-version - 2.263.1 workflow-api - 2.40 Datadog-plugin - 2.60.1	New: jenkins-version - 2.263.1 workflow-job - 2.40 Datadog-plugin - 2.60.1

Ajay Kumar made changes - 2021-01-22 10:06

Environment

Original: jenkins-version - 2.263.1 workflow-job - 2.40 Datadog-plugin - 2.60.1

New: jenkins-version - 2.263.1 workflow-job - 2.40 workflow-api - 2.40 Datadog-plugin - 2.60.1

Ajay Kumar made changes - 2021-01-22 10:07

Description

Original: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40*  After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.  We see multiple of these in our logs, which is similar to JENKINS-52362 {code:java} //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}

New: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40*  After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.  We see multiple of these in our logs, which is similar to JENKINS-52362 , however rolling back to *Datadog-plugin version 1.1* and using *workflow-job 2.37* does not create the issue anymore. {code:java} //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}

Collapse comment: Datadog HQ added a comment - 2021-02-03 16:00

Datadog HQ added a comment - 2021-02-03 16:00

Hello - this issue seems similar to one posted to GitHub here: https://github.com/jenkinsci/datadog-plugin/issues/170

We are posting version 2.8.1 of the Datadog plugin which includes a fix, can you try it out and see if that solves this problem as well?

Expand comment: Datadog HQ added a comment - 2021-02-03 16:00

Datadog HQ added a comment - 2021-02-03 16:00 Hello - this issue seems similar to one posted to GitHub here: https://github.com/jenkinsci/datadog-plugin/issues/170 We are posting version 2.8.1 of the Datadog plugin which includes a fix, can you try it out and see if that solves this problem as well?

Collapse comment: Ajay Kumar added a comment - 2021-02-03 16:24

Ajay Kumar added a comment - 2021-02-03 16:24

Thanks for letting us know, we will see if this solves our issue.  

Expand comment: Ajay Kumar added a comment - 2021-02-03 16:24

Ajay Kumar added a comment - 2021-02-03 16:24 Thanks for letting us know, we will see if this solves our issue.  

Collapse comment: Julia Simon added a comment - 2021-02-22 09:17

Julia Simon added a comment - 2021-02-22 09:17

Hallo akumarmandapati did you have a chance to check if it's working?

Expand comment: Julia Simon added a comment - 2021-02-22 09:17

Julia Simon added a comment - 2021-02-22 09:17 Hallo akumarmandapati  did you have a chance to check if it's working?

Collapse comment: Julia Simon added a comment - 2021-03-08 09:35

Julia Simon added a comment - 2021-03-08 09:35

Halo akumarmandapati, I'm closing this issue now. Please let us know if you are still experiencing this issue

Expand comment: Julia Simon added a comment - 2021-03-08 09:35

Julia Simon added a comment - 2021-03-08 09:35 Halo akumarmandapati , I'm closing this issue now. Please let us know if you are still experiencing this issue

Julia Simon made changes - 2021-03-08 09:36

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Collapse comment: Ajay Kumar added a comment - 2021-03-09 09:25

Ajay Kumar added a comment - 2021-03-09 09:25

Hey jsimon I am extremely sorry for responding late on this one!  I can confirm that the issue is solved now. 
Thanks!

Expand comment: Ajay Kumar added a comment - 2021-03-09 09:25

Ajay Kumar added a comment - 2021-03-09 09:25 Hey jsimon  I am extremely sorry for responding late on this one!  I can confirm that the issue is solved now.  Thanks!