Skip to content

PostgreSQL Auto-Upgrade failure handling should either halt the upgrade entirely or the warning about postgresqsl upgrade failure should be clear

Problem Description

Currently, there is lack of clarity about how the GitLab upgrade process should handle PostgreSQL auto-upgrade failures. The system needs a clear strategy for when the PostgreSQL auto-upgrade component fails during a GitLab upgrade.

Current Behavior

When PostgreSQL auto-upgrade fails, the behavior is undefined, leading to potential inconsistencies in the upgrade process.

Decision Required

We need to determine the appropriate response when PostgreSQL auto-upgrade fails:

Option 1: Halt entire GitLab upgrade

  • Pros: Prevents potential data inconsistencies
  • Cons: May leave the system in a half-configured state due to incomplete dpkg/yum package installation

Option 2: Continue with warning

  • Pros: Allows GitLab upgrade to complete
  • Cons: May result in version mismatches between GitLab and PostgreSQL

Considerations

  • Impact on system stability and data integrity
  • Package manager state (dpkg/yum) implications
  • User experience and recovery procedures
  • Clear communication of failure state to administrators

Acceptance Criteria

  • Define clear behavior for PostgreSQL auto-upgrade failures
  • Implement appropriate error handling and user notification
  • Document recovery procedures for failed scenarios
  • Ensure system remains in a recoverable state regardless of chosen approach

Description was generated using AI