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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Overview of the Issue
If a PR has a plan currently being run, and another change is force pushed, Atlantis will reply with The default workspace is currently locked by another command that is running for this pull request. Wait until the previous command is complete and try again.. When the original plan operation is completed, and atlantis apply is run, it results in Ran Apply for 0 projects:, despite there being changes in the original plan output.
Reproduction Steps
Open a PR with changes
While the plan is running, force push another change to the PR
Observe The default workspace is currently locked by another command that is running for this pull request. Wait until the previous command is complete and try again.
Wait until the original plan has commented it's changes
I am also running into this on v0.19.2. I commented also on issue: #773
I'm going to repeat that comment here, because I think it's relevant:
I am using an atlantis.yaml that was previously working. I think around v0.19.* this started breaking. It is about 50 projects, each with its own project name so that the -p wildcard flag can be used. The pattern for the naming is ${service_name}-${environment}.
I discovered that if i run atlantis apply -p *-environment, then the command will run, but it will run for ALL projects, regardless of what files have changed.
I have autoplan on, but if I run atlantis plan manually, it doesn't seem to make a difference.
Also of note, I am using custom workflows, not sure if that makes a difference.
Community Note
Overview of the Issue
If a PR has a plan currently being run, and another change is force pushed, Atlantis will reply with
The default workspace is currently locked by another command that is running for this pull request. Wait until the previous command is complete and try again.
. When the originalplan
operation is completed, andatlantis apply
is run, it results inRan Apply for 0 projects:
, despite there being changes in the original plan output.Reproduction Steps
The default workspace is currently locked by another command that is running for this pull request. Wait until the previous command is complete and try again.
atlantis apply
Ran Apply for 0 projects:
Logs
Logs
Environment details
Running in ECS with an EFS filesystem for consistency between container replacements
Environment
Atlantis.yaml
Additional Context
The text was updated successfully, but these errors were encountered: