[JIRA] (JENKINS-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum updated JENKINS-55170 Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Change By: Devin Nusbaum Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Josh Soref updated JENKINS-55170 Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Vivek Pandey commented on JENKINS-55170 Re: Failure to load flow node: FlowNode was not found in storage for head Sam Van Oort this llooks familiar and probably same as other issue you looked at? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title bentoi created an issue Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Issue Type: Bug Assignee: Unassigned Attachments: flowNodeStore.xml.bz2 Components: workflow-cps-plugin, workflow-job-plugin Created: 2018-12-13 09:27 Environment: Job plugin 2.29, Pipeline plugin 2.6 Priority: Minor Reporter: bentoi Jenkins is configured with the performance optimized durability setting. The master isn't restarted between builds. Slaves can be added and removed during the JOB execution. When the JOB fails, very frequently, Jenkins fails to load the results under Blueocean and logs the following error in the log. I've attached the corresponding flowNodeStore.xml WARNING: Error initializing storage and loading nodes, will try to create placeholders for: CpsFlowExecution[Owner[ice-dist/3.7/626:ice-dist/3.7 #626]] java.io.IOException: Tried to load head FlowNodes for execution Owner[ice-dist/3.7/626:ice-dist/3.7 #626] but FlowNode was not found in storage for head id:FlowNodeId 1:8180 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at