2023-08-12: Last successful WAL-G basebackup for postgres-ci-dr-archive-2004-01-db-gprd.c.gitlab-production.internal was seen 33.58 hours ago for env gprd
Customer Impact
No customer impact.
Current Status
Last successful WAL-G basebackup for postgres-ci-dr-archive-2004-01-db-gprd.c.gitlab-production.internal was seen 33.58 hours ago for env gprd.
WAL-G backup-push creating full backups and archiving them to GCS might be not working.
This is a known issue from the PG14 Upgrade work from earlier today.
See Epic: &802 (closed)
See tracking issue: #16093 (closed)
See production change plan: https://ops.gitlab.net/gitlab-com/gl-infra/db-migration/-/issues/63
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates.
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in our handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.