-
Notifications
You must be signed in to change notification settings - Fork 9
Description
A recent error has been noted where the current database-postgres fails to start after trigger a new deployment on an existing deployment.
The database-postgres packages makes use of version 14 of the supplied images. A few days ago, a new has was built under the same tag version which introduced a breaking change on existing deployments.
https://hub.docker.com/layers/bitnami/postgresql/14/images/sha256-bd397924167c093826e9674ef463215acddf662985ca8120a80839daf53e3f67?context=explore
The new version 14 hash requires an updated repmgr version to be installed and used. Because this isnt installed in the current version, the container fails to start up, and thus prevents other services from starting up
2024-12-02 16:39:13.818 GMT [141] LOG: redo is not required
2024-12-02 16:39:13.846 GMT [158] FATAL: the database system is starting up
2024-12-02 16:39:14.868 GMT [161] FATAL: the database system is starting up
2024-12-02 16:39:15.266 GMT [137] LOG: database system is ready to accept connections
postgresql-repmgr 16:39:15.88 INFO ==> ** Starting repmgrd **
[2024-12-02 16:39:15] [NOTICE] repmgrd (repmgrd 5.5.0) starting up
[2024-12-02 16:39:15] [ERROR] an older version of the "repmgr" extension is installed
[2024-12-02 16:39:15] [DETAIL] extension version 5.4 is installed but newer version 5.5 is available
[2024-12-02 16:39:15] [HINT] verify the repmgr installation is updated properly before continuing
Temp Fix:
Pin the specific hash version before the change occurred to ensure the database can start up under the old version
POSTGRES_IMAGE=bitnami/postgresql-repmgr:14@sha256:bdf1e4903710c4e0b465664b886d4556897e1b18c07d7c513a4fc1ceba929e02