Rollback pipeline for the canary stage does not operate nor behave similar to that of the main stage
We recently did a rollback of the canary stage due to production#7284 (closed) not reaching the main stage. Best course of action at the time was to perform a rollback of Gitaly. The pipeline for the canary stage does not operate as we document. Utilize this issue to track the changes necessary to update the pipeline such that it behaves and acts similar to that of the main stage. Currently this pipeline does not rollback Praefect, Gitaly is not optional, Kubernetes is updated AFTER Gitaly, and QA automatically runs. Example screenshots from the most recently run rollback that occurred on Canary:
And then our staging rollback look as desired:
References:
- Canary Pipeline: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/1270410
- Staging Rollback Practice: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/pipelines/1247093