You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we see that the "put" step tries to acquire the lock for longer than 4 hours. Eventually, the lock is acquired and the state in the git repo is correctly updated. However, as the timeout is exceeded, Concourse shows the job as failed (red) and downstream jobs are not triggered:
The expectation is that the jobs fails after 4 hours and the lock is not acquired.
Reproduction steps
Create a pipeline with the resource and job shown above.
Put the lock in "claimed" state.
Trigger the "acquire-pool" job.
Wait until timeout has passed.
Put the lock in "unclaimed" state.
The "acquire-pool" job should now claim the lock and fail.
Expected behavior
When the timeout has passed, the acquire job should fail and should not make any changes on the pool's state.
Additional context
On Concourse v7.9.0 with pool-resource v1.3.1 we don't observe this behaviour.
The text was updated successfully, but these errors were encountered:
Describe the bug
We are observing a strange behaviour on Concourse v7.10.0 with pool-resource v1.4.0. We are trying to acquire locks in our pipeline like this:
Now we see that the "put" step tries to acquire the lock for longer than 4 hours. Eventually, the lock is acquired and the state in the git repo is correctly updated. However, as the timeout is exceeded, Concourse shows the job as failed (red) and downstream jobs are not triggered:
The expectation is that the jobs fails after 4 hours and the lock is not acquired.
Reproduction steps
Create a pipeline with the resource and job shown above.
Put the lock in "claimed" state.
Trigger the "acquire-pool" job.
Wait until timeout has passed.
Put the lock in "unclaimed" state.
The "acquire-pool" job should now claim the lock and fail.
Expected behavior
When the timeout has passed, the acquire job should fail and should not make any changes on the pool's state.
Additional context
On Concourse v7.9.0 with pool-resource v1.3.1 we don't observe this behaviour.
The text was updated successfully, but these errors were encountered: