Default Auto Devops deployments fail unless AUTO_DEVOPS_POSTGRES_CHANNEL=1
Summary
Pipelines started failing recently when we switched postgres channels. On both the version.GitLab.com
app and the license.GitLab.com
app where we are dogfooding Auto Devops, we now have to set AUTO_DEVOPS_POSTGRES_CHANNEL=1
in order for any deployments to succeed - including freshly pushed new branches.
- This caused pipelines to fail on this MR: https://gitlab.com/gitlab-org/license-gitlab-com/-/merge_requests/151
Steps to reproduce
- Push a branch on https://gitlab.com/gitlab-org/license-gitlab-com or https://gitlab.com/gitlab-services/version-gitlab-com
- Wait for the review stage to fail
- Check the bottom of the job for error messages about the postgres channel: https://gitlab.com/gitlab-org/license-gitlab-com/-/jobs/563045414
Example Project
- https://gitlab.com/gitlab-org/license-gitlab-com
- https://gitlab.com/gitlab-services/version-gitlab-com
What is the current bug behavior?
- Existing deployments ask to set
AUTO_DEVOPS_POSTGRES_DELETE_V1
(https://gitlab.com/gitlab-org/license-gitlab-com/-/jobs/568749716), which does not work (https://gitlab.com/gitlab-org/license-gitlab-com/-/jobs/568772208) - Fresh deployments fail (https://gitlab.com/gitlab-org/license-gitlab-com/-/jobs/563045414)
- Setting
AUTO_DEVOPS_POSTGRES_CHANNEL=1
allows the pipelines to succeed (https://gitlab.com/gitlab-org/license-gitlab-com/-/jobs/568809980), but this is not the default behavior
What is the expected correct behavior?
Pipelines should succeed by default, whether that is with the old postgres channel or the new.
Relevant logs and/or screenshots
See the job outputs linked above
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)