concourse / concourse/pool-resource
Claims environment but task never finishes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
This just started happening a lot on the Opsmanager pipeline.
It says it claims the environment, and the 2nd step of the job succeeds, but the 1st step of the job never stops running.
This build (below) has been running for 5 hours before we noticed it stuck on claiming the environment.
For our reference, if I want to look up this example again:
https://om.ci.cf-app.com/teams/main/pipelines/opsmanager-1.8/jobs/openstack-clean-install-external/builds/24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced Opsmanager pipeline build 24 and compare the environment-claiming step with the succeeding second step. Trace why the first step remains running; done means the task no longer hangs while claiming the environment and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100