[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Mihai Stoichitescu commented on JENKINS-60507 Re: Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled We are still being hit by the issue from time to time, any ideas/workarounds/help to debug would be appreciated. Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.8706.1584520680119%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Mihai Stoichitescu commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head We are also getting this from time to time after updating Jenkins from 2.121.3 to 2.190.1 I've attached a list of our plugins used. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.2981.1578336720796%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Mihai Stoichitescu updated an issue Jenkins / JENKINS-55287 Pipeline: Failure to load flow node: FlowNode was not found in storage for head Change By: Mihai Stoichitescu Attachment: plugins_versions_2.190.1.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.2943.1578336001061%40Atlassian.JIRA.
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title
Mihai Stoichitescu updated an issue
Jenkins / JENKINS-60507
Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Change By:
Mihai Stoichitescu
Our build system is sometimes showing this in the Thread Dump of a Pipeline while waiting for free executors {code:java}Thread #94at DSL.node(node block appears to be neither running nor scheduled)at WorkflowScript.runOnNode(WorkflowScript:1798)at DSL.timeout(body has another 3 hr 14 min to run)at WorkflowScript.runOnNode(WorkflowScript:1783)at DSL.retry(Native Method)at WorkflowScript.runOnNode(WorkflowScript:1781)at WorkflowScript.getClosure(WorkflowScript:1901){code} In BlueOcean this appears, but the build queue is empty, and executors are available with those labels. {code:java}Still waiting to schedule taskWaiting for next available executor on pr&&&{code} The job can only be completed by aborting or waiting for the timeout step to do it’s work. We started observing it since v2.121.3 (workflow-durable-task-step v2.19) but recently we updated to v2.190.1 (workflow-durable-task-step v2.28) and still seeing stuck pipelines when waiting for executors. The only reference I could find was in the last comment of this issue: https://issues.jenkins-ci.org/browse/JENKINS-42556 and there’s no way we can reproduce it. We’ve noticed this fix made by [~jglick] but not sure if it will help us. We tried turning on Anonymous for a week and we still saw the problem. Please let me know if there’s more information/logs that I can help with to track down what might be the cause of this. Thanks. I've attached _FINEST_ level logs on _hudson.model.Queue_, not sure if that will help a lot. Our Jenkins runs on RedHat, on Tomcat/9.0.14 and Java 1.8.0_171.
Add Comment
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Mihai Stoichitescu updated an issue Jenkins / JENKINS-60507 Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled Change By: Mihai Stoichitescu Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.8929.1576510561530%40Atlassian.JIRA.
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Mihai Stoichitescu created an issue Jenkins / JENKINS-60507 Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled Issue Type: Bug Assignee: Unassigned Attachments: plugins_versions.txt, queue.logs.zip Components: core, workflow-durable-task-step-plugin Created: 2019-12-16 15:33 Priority: Minor Reporter: Mihai Stoichitescu Our build system is sometimes showing this in the Thread Dump of a Pipeline while waiting for free executors Thread #94 at DSL.node(node block appears to be neither running nor scheduled) at WorkflowScript.runOnNode(WorkflowScript:1798) at DSL.timeout(body has another 3 hr 14 min to run) at WorkflowScript.runOnNode(WorkflowScript:1783) at DSL.retry(Native Method) at WorkflowScript.runOnNode(WorkflowScript:1781) at WorkflowScript.getClosure(WorkflowScript:1901) In BlueOcean this appears, but the build queue is empty, and executors are available with those labels. Still waiting to schedule task Waiting for next available executor on pr&&& The job can only be completed by aborting or waiting for the timeout step to do it’s work. We started observing it since v2.121.3
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu commented on JENKINS-42860 Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Albert V This does not appear on `In-process Script Approval` unfortunately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu assigned an issue to Mihai Stoichitescu Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Mihai Stoichitescu Assignee: Kohsuke Kawaguchi Mihai Stoichitescu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Mihai Stoichitescu Assignee: Mihai Stoichitescu Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Mihai Stoichitescu commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Thorsten Meinl we encounter this error on machines that only have 1 executor setup. Maybe this happens if there are flyweight executors running on the node? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
