jenkinsci / jenkinsci/durable-task-plugin
[JENKINS-72365] Pipeline Stuck in "Ready to Run" Status After Jenkins Restart
- Dominant language
- Java
- Stars
- 30
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
This is my jenkins pipeline script:
pipeline {
agent any
stages {
stage('Hello1') {
steps {
sh 'echo hello1'
}
}
stage('sleep') {
steps {
retry(2) {
sh 'sleep 20'
}
}
}
stage('Hello2') {
steps {
sh 'echo hello2'
}
}
}
}
In our Jenkins environment, we encounter an issue where pipeline jobs fail to proceed after a Jenkins service restart. Specifically, the pipeline becomes stuck at a stage following a sleep command, with the log file showing "Ready to run" but no further activity. This issue arises under a configuration where Jenkins is run within a Podman container. We have verified that the durability settings are configured for high reliability, yet the problem persists.
Additionally, the logs indicate a warning suggesting an increase in the org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL value if the filesystem is exceedingly slow. Following this advice, we attempted to set this value to 86400, but to no avail, the issue remains unresolved.
---
Originally reported by leechehao, imported from: Pipeline Stuck in "Ready to Run" Status After Jenkins Restart
Raw content of original issue
This is my jenkins pipeline script:
pipeline {
agent any
stages {
stage('Hello1') {
steps {
sh 'echo hello1'
}
}
stage('sleep') {
steps {
retry(2) {
sh 'sleep 20'
}
}
}
stage('Hello2') {
steps {
sh 'echo hello2'
}
}
}
}In our Jenkins environment, we encounter an issue where pipeline jobs fail to proceed after a Jenkins service restart. Specifically, the pipeline becomes stuck at a stage following a sleep command, with the log file showing "Ready to run" but no further activity. This issue arises under a configuration where Jenkins is run within a Podman container. We have verified that the durability settings are configured for high reliability, yet the problem persists.
Additionally, the logs indicate a warning suggesting an increase in the org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL value if the filesystem is exceedingly slow. Following this advice, we attempted to set this value to 86400, but to no avail, the issue remains unresolved.
environment
```
Jenkins 2.426.1
docker image -> jenkins/jenkins:2.426.1-jdk17
Durable Task Plugin 523.va_a_22cf15d5e0
```
1 attachment
- [log.txt](https://issues.jenkins.io/secure/attachment/61608/log.txt)
Contributor guide
Assessment
This issue has not been assessed yet.