Claims environment but task never finishes

concourse / pool-resource

atomically manages the state of the world (e.g. external environments)

Apache License 2.0

54 stars 36 forks source link

Open ameowlia opened 7 years ago

ameowlia commented 7 years ago

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.

concourse-bot commented 7 years ago

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

vito commented 7 years ago

looks like something interrupted the progress of the build on the worker, so it re-started from scratch and tried acquiring again.

concourse version?

ameowlia commented 7 years ago

concourse version: v2.6.0

We're still seeing this pretty regularly.

Here's another, slightly different, example.

the first half of the environment task never technically finished, even though the second half did, and even though it claimed an environment and moved on to the next step.
we decided to kill this job for unrelated reasons
the environment is never able to be released and we had an environment in limbo

marco-m commented 5 years ago

@ameowlia is this still happening? Did you upgraded your Concourse version in the meantime ?