Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Claims environment but task never finishes #26

Open
ameowlia opened this issue Feb 27, 2017 · 4 comments
Open

Claims environment but task never finishes #26

ameowlia opened this issue Feb 27, 2017 · 4 comments
Labels

Comments

@ameowlia
Copy link

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.

image

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

@concourse-bot
Copy link
Collaborator

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:

  • #140716827 Claims environment but task never finishes

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

@vito
Copy link
Member

vito commented Feb 28, 2017

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
Copy link
Author

ameowlia commented Mar 8, 2017

concourse version: v2.6.0

We're still seeing this pretty regularly.

Here's another, slightly different, example.

image

  • 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

@vito vito removed the unscheduled label May 9, 2017
@chendrix chendrix added the bug label May 24, 2017
@marco-m
Copy link
Contributor

marco-m commented Oct 13, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants