On a self host gitlab running atlantis 0.27.2, the...
# atlantis-community
t
On a self host gitlab running atlantis 0.27.2, the
atlantis/apply
job isn’t created. Can anyone provide some hints where to look?
j
we have this issue all the time.
There is no solution except to restart atlantis until it starts showing up again.
If you enable debug logging at atlantis, maybe you can catch something, ive never been able to get debug on, and have it fail.
t
Are you on the latest version of atlantis?
j
Yes
but the problem has happened for multiple releases
and multiple gitlab releases
t
I’m not getting it at all during autoplans. I believe it worked for me in 0.24.x and it broke after i upgraded. I’m not running it in prod so my experience is limited. I’m looking into the issue, i’ve added some debugging and running it right now.
Steps I take: • Create a new merge request that creates a new resources. (I’m using
resource "terraform_data" "example" {}
) • Atlantis autoplans, creating an external stage with
atlantis/plan
,
atlantis/plan: <project>
, and
atlantis/policy_check
jobs. I expect there to be a pending
atlantis/apply
job to prevent the merge request from being merged. I think it has to do with https://github.com/runatlantis/atlantis/pull/3378 and then the followup https://github.com/runatlantis/atlantis/pull/3747. In my test case updateCommitStatus returns without updating the apply status because of the <https://github.com/runatlantis/atlantis/blob/main/server/events/plan_command_runner.go#L331%7Celse if numSuccess < len(pullStatus.Projects)> check.
j
We do not get a
apply
pipeline, until we
atlantis apply
We cant apply until the pipeline is approved, and we cant merge until all pipelines have ran successfully. So i see the same behavior you have, but its not a problem for us.
t
Are you able to merge in-between the merge request is approved but before
atlantis apply
is ran?
j
Only before
atlantis apply
is typed
t
So someone can create a merge request and merge it in without
atlantis apply
running, right?
j
Yes
🙏 1