concourse / pool-resource

atomically manages the state of the world (e.g. external environments)
Apache License 2.0
56 stars 36 forks source link

Claiming lock on .gitkeep file #3

Closed shashwathi closed 9 years ago

shashwathi commented 9 years ago

We have a job which acquired lock on .gitkeep file and it failed to release the lock at end of pipeline. I have attached snippets for acquiring lock and error for releasing lock. screen shot 2015-08-12 at 10 23 32 am screen shot 2015-08-12 at 10 26 44 am

concourse-bot commented 9 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.

xoebus commented 9 years ago

@shashwathi I think you're missing a passed constraint on this job referring to the job that acquired the lock?

shashwathi commented 9 years ago

@xoebus After looking at our config again, looks like we had an unnecessary get before the initial put + acquire (stars for emphasis). After removing this line things work as expected. Closing this out.

- name: claim-a1-environment
  plan:
  - aggregate:
    - get: cf-mysql-release
      passed:
      # all bosh-lite pipelines
      - release-upgrade-environment
      - release-failover-environment
      - release-scaling-environment
      trigger: true
    - **get: aws-integration-environment**
  - put: aws-integration-environment
    params:
      acquire: true