charts Postgres-HA not able to upgrade 8.0.0

Name and Version

bitnami/postgres-ha 8.*

What steps will reproduce the bug?

Install postgres-ha in version 7.12

try to upgrade it to 8.* with

    --set postgresql.replicaCount=1 \
    --set postgresql.upgradeRepmgrExtension=true

Postgres wont upgrade correctly

Are you using any custom parameters or values?

postgresql.repmgrPassword
pgpool.adminPassword
postgresql.password

global:
  postgresql:
    username: "postgres"

clusterDomain: cluster.local

postgresql:
  replicaCount: 1
  maxConnections: 500
  dbUserConnectionLimit: 300
  upgradeRepmgrExtension: true
postgresqlImage:
    debug: true

serviceAccount:
  enabled: true

metrics:
  enabled: true
  serviceMonitor:
    enabled: true

persistence:
  storageClass: "managed-nfs-storage"

pgpool:
  replicaCount: 3

What is the expected behavior?

postgres-0 starts, upgrade repmgr and i can scale the env to tree again

What do you see instead?

postgresql-repmgr 11:57:35.54
postgresql-repmgr 11:57:35.54 Welcome to the Bitnami postgresql-repmgr container
postgresql-repmgr 11:57:35.54 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql-repmgr
postgresql-repmgr 11:57:35.54 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql-repmgr/issues
postgresql-repmgr 11:57:35.54
postgresql-repmgr 11:57:35.55 DEBUG ==> Configuring libnss_wrapper...
postgresql-repmgr 11:57:35.56 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
postgresql-repmgr 11:57:35.60 INFO  ==> Validating settings in REPMGR_* env vars...
postgresql-repmgr 11:57:35.60 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql-repmgr 11:57:35.60 INFO  ==> Querying all partner nodes for common upstream node...
postgresql-repmgr 11:57:35.61 DEBUG ==> Checking node 'postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local:5432'...
psql: could not connect to server: Connection refused
        Is the server running on host "postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" (10.42.5.190) and accepting
        TCP/IP connections on port 5432?
postgresql-repmgr 11:57:35.63 DEBUG ==> Skipping: failed to get primary from the node 'postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local:5432'!
postgresql-repmgr 11:57:35.63 INFO  ==> There are no nodes with primary role. Assuming the primary role...
postgresql-repmgr 11:57:35.64 INFO  ==> Preparing PostgreSQL configuration...
postgresql-repmgr 11:57:35.64 DEBUG ==> Injecting a new postgresql.conf file...
postgresql-repmgr 11:57:35.65 INFO  ==> postgresql.conf file not detected. Generating it...
postgresql-repmgr 11:57:35.76 DEBUG ==> Injecting a new pg_hba.conf file...
postgresql-repmgr 11:57:36.39 INFO  ==> Preparing repmgr configuration...
postgresql-repmgr 11:57:36.41 DEBUG ==> Node ID: '1000', Rol: 'primary', Primary Node: ':5432'
postgresql-repmgr 11:57:36.41 INFO  ==> Initializing Repmgr...
postgresql-repmgr 11:57:36.42 INFO  ==> Initializing PostgreSQL database...
postgresql-repmgr 11:57:36.42 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
postgresql-repmgr 11:57:36.43 DEBUG ==> Copying files from /bitnami/postgresql/conf to /opt/bitnami/postgresql/conf
postgresql-repmgr 11:57:36.43 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/postgresql.conf detected
postgresql-repmgr 11:57:36.44 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
postgresql-repmgr 11:57:36.44 DEBUG ==> Ensuring expected directories/files exist...
postgresql-repmgr 11:57:36.47 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql-repmgr 11:57:36.49 INFO  ==> Configuring replication parameters
postgresql-repmgr 11:57:36.53 INFO  ==> Configuring fsync
postgresql-repmgr 11:57:36.54 INFO  ==> Starting PostgreSQL in background...
waiting for server to start....2022-09-21 11:57:36.575 GMT [152] LOG:  pgaudit extension initialized
2022-09-21 11:57:36.576 GMT [152] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-09-21 11:57:36.576 GMT [152] LOG:  listening on IPv6 address "::", port 5432
2022-09-21 11:57:36.583 GMT [152] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-09-21 11:57:36.613 GMT [152] LOG:  redirecting log output to logging collector process
2022-09-21 11:57:36.613 GMT [152] HINT:  Future log output will appear in directory "/opt/bitnami/postgresql/logs".
2022-09-21 11:57:36.617 GMT [154] LOG:  database system was interrupted while in recovery at log time 2022-09-21 11:41:44 GMT
2022-09-21 11:57:36.617 GMT [154] HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
....2022-09-21 11:57:41.276 GMT [154] LOG:  entering standby mode
2022-09-21 11:57:41.288 GMT [154] LOG:  redo starts at 0/6E00BAA0
2022-09-21 11:57:41.288 GMT [154] LOG:  consistent recovery state reached at 0/6F000000
2022-09-21 11:57:41.289 GMT [152] LOG:  database system is ready to accept read only connections
2022-09-21 11:57:41.301 GMT [158] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
2022-09-21 11:57:41.307 GMT [159] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
 done
server started
postgresql-repmgr 11:57:41.33 INFO  ==> Upgrading repmgr extension...
2022-09-21 11:57:41.373 GMT [166] ERROR:  cannot execute ALTER EXTENSION in a read-only transaction
ERROR:  cannot execute ALTER EXTENSION in a read-only transaction
2022-09-21 11:57:41.373 GMT [166] STATEMENT:  ALTER EXTENSION repmgr UPDATE
postgresql-repmgr 11:57:41.37 INFO  ==> Stopping PostgreSQL...
waiting for server to shut down...2022-09-21 11:57:41.384 GMT [152] LOG:  received fast shutdown request
.2022-09-21 11:57:41.385 GMT [152] LOG:  aborting any active transactions
2022-09-21 11:57:41.386 GMT [155] LOG:  shutting down
2022-09-21 11:57:41.400 GMT [152] LOG:  database system is shut down
 done
server stopped
postgresql-repmgr 11:57:41.49 INFO  ==> ** PostgreSQL with Replication Manager setup finished! **

postgresql-repmgr 11:57:41.52 INFO  ==> Starting PostgreSQL in background...
waiting for server to start....2022-09-21 11:57:41.556 GMT [181] LOG:  pgaudit extension initialized
2022-09-21 11:57:41.557 GMT [181] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-09-21 11:57:41.557 GMT [181] LOG:  listening on IPv6 address "::", port 5432
2022-09-21 11:57:41.560 GMT [181] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-09-21 11:57:41.589 GMT [181] LOG:  redirecting log output to logging collector process
2022-09-21 11:57:41.589 GMT [181] HINT:  Future log output will appear in directory "/opt/bitnami/postgresql/logs".
2022-09-21 11:57:41.593 GMT [183] LOG:  database system was shut down in recovery at 2022-09-21 11:57:41 GMT
2022-09-21 11:57:41.594 GMT [183] LOG:  entering standby mode
2022-09-21 11:57:41.607 GMT [183] LOG:  redo starts at 0/6E00BAA0
2022-09-21 11:57:41.607 GMT [183] LOG:  consistent recovery state reached at 0/6F000000
2022-09-21 11:57:41.608 GMT [181] LOG:  database system is ready to accept read only connections
2022-09-21 11:57:41.614 GMT [187] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
2022-09-21 11:57:41.620 GMT [188] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
 done
server started
postgresql-repmgr 11:57:41.65 INFO  ==> ** Starting repmgrd **
[2022-09-21 11:57:41] [NOTICE] repmgrd (repmgrd 5.3) starting up
[2022-09-21 11:57:41] [ERROR] an older version of the "repmgr" extension is installed
[2022-09-21 11:57:41] [DETAIL] extension version 5.2 is installed but newer version 5.3 is available
[2022-09-21 11:57:41] [HINT] verify the repmgr installation is updated properly before continuing

Additional information

Helm Rollback is working, so at least the Database is still running with Helm Chart version7.*

Sep 21 '22 11:09 pascalrimann

Could you take a look at https://github.com/bitnami/charts/tree/master/bitnami/postgresql-ha#upgrading and https://github.com/bitnami/charts/tree/master/bitnami/postgresql-ha#to-800? Let us know if following those instructions you are able to solve the issue

Sep 21 '22 13:09 carrodher

yes i set them, it does not help

Sep 21 '22 14:09 pascalrimann

@carrodher do you have any idea?

Sep 23 '22 06:09 pascalrimann

@rafariossaa do you have an idea?

Sep 26 '22 06:09 pascalrimann

Hi, Sorry for the delay. Have you tried what is indicated here ? The error regarding repmgr version is avoided when using --set postgresql.upgradeRepmgrExtension=true I tried this and it worked for me:

$ helm pull helm pull bitnami-full-gh/postgresql-ha --version=7.12
$ mkdir 7
$ cd 7
$ tar -xf ../postgresql-ha-7.12.5.tgz
$ cd postgresql-ha
$ helm install mypg  -f values.yaml \
  --set postgresql.repmgrPassword=testpwd1 \
  --set pgpool.adminPassword=testpwd2 \
  --set postgresql.password=testpwd3 \
  --set postgresql.replicaCount=1 \
  --set pgpool.replicaCount=3 \
  .

$ helm pull helm pull bitnami-full-gh/postgresql-ha --version=8.0
$ mkdir 8
$ cd 8
$ tar -xf ../postgresql-ha-8.0.5.tgz
$ cd postgresql-ha
$ helm upgrade mypg  -f values.yaml \
  --set postgresql.repmgrPassword=testpwd1 \
  --set pgpool.adminPassword=testpwd2 \
  --set postgresql.password=testpwd3 \
  --set postgresql.replicaCount=1 \
  --set pgpool.replicaCount=3 \
  --set postgresql.upgradeRepmgrExtension=true \
  .

Sep 26 '22 08:09 rafariossaa

@rafariossaa yes i used the value from the values.yaml:

postgresql:
  replicaCount: 1
  maxConnections: 500
  dbUserConnectionLimit: 300
  upgradeRepmgrExtension: true
postgresqlImage:
    debug: true

after that i upgrade with the Gitlab Ci using this commands:

$ export REPMGR_PASSWORD=$(kubectl get secret --kubeconfig kubeconfig.yaml --namespace "${namespace}" postgresha-postgresql-ha-postgresql -o jsonpath="{.data.repmgr-password}" | base64 -d)
$ export ADMIN_PASSWORD=$(kubectl get secret --kubeconfig kubeconfig.yaml --namespace "${namespace}" postgresha-postgresql-ha-pgpool -o jsonpath="{.data.admin-password}" | base64 -d)
$ export POSTGRESQL_PASSWORD=$(kubectl get secret --kubeconfig kubeconfig.yaml --namespace "${namespace}" postgresha-postgresql-ha-postgresql -o jsonpath="{.data.postgresql-password}" | base64 -d)
$ helm upgrade --install --version "${PSQLHA_CHART_VERSION}" --kubeconfig kubeconfig.yaml --values values/postgres-ha-"${namespace}".yaml --values secrets.yaml --set postgresql.repmgrPassword=$REPMGR_PASSWORD --set pgpool.adminPassword=$ADMIN_PASSWORD --set postgresql.password=$POSTGRESQL_PASSWORD --namespace "${namespace}" postgresha bitnami/postgresql-ha

there i get this Output:

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: kubeconfig.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: kubeconfig.yaml
Release "postgresha" has been upgraded. Happy Helming!
NAME: postgresha
LAST DEPLOYED: Wed Sep 21 11:54:15 2022
NAMESPACE: harbor-test
STATUS: deployed
REVISION: 25
TEST SUITE: None
NOTES:
CHART NAME: postgresql-ha
CHART VERSION: 8.1.5
APP VERSION: 11.14.0
** Please be patient while the chart is being deployed **
PostgreSQL can be accessed through Pgpool via port 5432 on the following DNS name from within your cluster:
    postgresha-postgresql-ha-pgpool.harbor-test.svc.cluster.local
Pgpool acts as a load balancer for PostgreSQL and forward read/write connections to the primary node while read-only connections are forwarded to standby nodes.
To get the password for "postgres" run:
    export POSTGRES_PASSWORD=$(kubectl get secret --namespace harbor-test postgresha-postgresql-ha-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
To get the password for "repmgr" run:
    export REPMGR_PASSWORD=$(kubectl get secret --namespace harbor-test postgresha-postgresql-ha-postgresql -o jsonpath="{.data.repmgr-password}" | base64 --decode)
To connect to your database run the following command:
    kubectl run postgresha-postgresql-ha-client --rm --tty -i --restart='Never' --namespace harbor-test --image docker.io/bitnami/postgresql-repmgr:11.14.0-debian-10-r47 --env="PGPASSWORD=$POSTGRES_PASSWORD"  \
        --command -- psql -h postgresha-postgresql-ha-pgpool -p 5432 -U postgres -d postgres
To connect to your database from outside the cluster execute the following commands:
    kubectl port-forward --namespace harbor-test svc/postgresha-postgresql-ha-pgpool 5432:5432 &
    psql -h 127.0.0.1 -p 5432 -U postgres -d postgres
Cleaning up project directory and file based variables

but somehow the DB does only start in ReadOnly, as seen in my log above and the ALTER Command does not work.

As I can see in your Output, you are using version 8.0, in the normal Repo there is only the chart Version 8.1 or newer. Could it be an issue that the upgrade does only work with version 8.0?

Sep 26 '22 09:09 pascalrimann

I tested it again creating a table and inserting data in version 7, and after upgrading to v8 I could insert more data into the table without issues.

I used the full index from here: https://github.com/bitnami/charts/issues/10833

Sep 27 '22 07:09 rafariossaa

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

Oct 13 '22 01:10 github-actions[bot]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

Oct 18 '22 01:10 github-actions[bot]

Hi, sorry for late respond, but even with version 8.0.0:

rimannp@bsp-devops-rimannp:~> k logs -n harbor-test postgresha-postgresql-ha-postgresql-0 postgresql
postgresql-repmgr 14:08:52.46
postgresql-repmgr 14:08:52.46 Welcome to the Bitnami postgresql-repmgr container
postgresql-repmgr 14:08:52.47 Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql-repmgr
postgresql-repmgr 14:08:52.47 Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql-repmgr/issues
postgresql-repmgr 14:08:52.47
postgresql-repmgr 14:08:52.47 DEBUG ==> Configuring libnss_wrapper...
postgresql-repmgr 14:08:52.49 INFO  ==> ** Starting PostgreSQL with Replication Manager setup **
postgresql-repmgr 14:08:52.52 INFO  ==> Validating settings in REPMGR_* env vars...
postgresql-repmgr 14:08:52.52 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql-repmgr 14:08:52.52 INFO  ==> Querying all partner nodes for common upstream node...
postgresql-repmgr 14:08:52.53 DEBUG ==> Checking node 'postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local:5432'...
postgresql-repmgr 14:08:52.54 DEBUG ==> Executing SQL command:
SELECT conninfo FROM repmgr.show_nodes WHERE (upstream_node_name IS NULL OR upstream_node_name = '') AND active=true
psql: could not connect to server: Connection refused
        Is the server running on host "postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" (10.42.3.164) and accepting
        TCP/IP connections on port 5432?
postgresql-repmgr 14:08:52.55 DEBUG ==> Skipping: failed to get primary from the node 'postgresha-postgresql-ha-postgresql-0.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local:5432'!
postgresql-repmgr 14:08:52.55 INFO  ==> There are no nodes with primary role. Assuming the primary role...
postgresql-repmgr 14:08:52.56 INFO  ==> Preparing PostgreSQL configuration...
postgresql-repmgr 14:08:52.56 DEBUG ==> Injecting a new postgresql.conf file...
postgresql-repmgr 14:08:52.57 INFO  ==> postgresql.conf file not detected. Generating it...
postgresql-repmgr 14:08:52.67 DEBUG ==> Injecting a new pg_hba.conf file...
postgresql-repmgr 14:08:52.67 INFO  ==> Preparing repmgr configuration...
postgresql-repmgr 14:08:52.69 DEBUG ==> Node ID: '1000', Rol: 'primary', Primary Node: ':5432'
postgresql-repmgr 14:08:52.69 INFO  ==> Initializing Repmgr...
postgresql-repmgr 14:08:52.70 INFO  ==> Initializing PostgreSQL database...
postgresql-repmgr 14:08:52.70 INFO  ==> Cleaning stale /bitnami/postgresql/data/postmaster.pid file
postgresql-repmgr 14:08:52.71 DEBUG ==> Copying files from /bitnami/postgresql/conf to /opt/bitnami/postgresql/conf
postgresql-repmgr 14:08:52.71 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/postgresql.conf detected
postgresql-repmgr 14:08:52.71 INFO  ==> Custom configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
postgresql-repmgr 14:08:52.72 DEBUG ==> Ensuring expected directories/files exist...
postgresql-repmgr 14:08:52.75 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql-repmgr 14:08:52.77 INFO  ==> Configuring replication parameters
postgresql-repmgr 14:08:52.80 INFO  ==> Configuring fsync
postgresql-repmgr 14:08:52.81 INFO  ==> Starting PostgreSQL in background...
waiting for server to start....2022-10-18 14:08:52.845 GMT [154] LOG:  pgaudit extension initialized
2022-10-18 14:08:52.846 GMT [154] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-10-18 14:08:52.846 GMT [154] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 14:08:52.870 GMT [154] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-10-18 14:08:52.901 GMT [154] LOG:  redirecting log output to logging collector process
2022-10-18 14:08:52.901 GMT [154] HINT:  Future log output will appear in directory "/opt/bitnami/postgresql/logs".
2022-10-18 14:08:52.905 GMT [156] LOG:  database system was interrupted while in recovery at log time 2022-10-18 06:19:06 GMT
2022-10-18 14:08:52.905 GMT [156] HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
....2022-10-18 14:08:57.651 GMT [156] LOG:  entering standby mode
2022-10-18 14:08:57.666 GMT [156] LOG:  redo starts at 0/A8274388
2022-10-18 14:08:57.666 GMT [156] LOG:  consistent recovery state reached at 0/A8274468
2022-10-18 14:08:57.666 GMT [156] LOG:  invalid record length at 0/A8274468: wanted 24, got 0
2022-10-18 14:08:57.667 GMT [154] LOG:  database system is ready to accept read only connections
2022-10-18 14:08:57.678 GMT [160] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
2022-10-18 14:08:57.684 GMT [161] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
 done
server started
postgresql-repmgr 14:08:57.76 INFO  ==> Upgrading repmgr extension...
postgresql-repmgr 14:08:57.77 DEBUG ==> Executing SQL command:
ALTER EXTENSION repmgr UPDATE
ERROR:  cannot execute ALTER EXTENSION in a read-only transaction
2022-10-18 14:08:57.800 GMT [170] ERROR:  cannot execute ALTER EXTENSION in a read-only transaction
2022-10-18 14:08:57.800 GMT [170] STATEMENT:  ALTER EXTENSION repmgr UPDATE
postgresql-repmgr 14:08:57.80 INFO  ==> Stopping PostgreSQL...
waiting for server to shut down...2022-10-18 14:08:57.810 GMT [154] LOG:  received fast shutdown request
.2022-10-18 14:08:57.811 GMT [154] LOG:  aborting any active transactions
2022-10-18 14:08:57.812 GMT [157] LOG:  shutting down
2022-10-18 14:08:57.824 GMT [154] LOG:  database system is shut down
 done
server stopped
postgresql-repmgr 14:08:57.91 INFO  ==> ** PostgreSQL with Replication Manager setup finished! **

postgresql-repmgr 14:08:57.94 INFO  ==> Starting PostgreSQL in background...
waiting for server to start....2022-10-18 14:08:57.974 GMT [185] LOG:  pgaudit extension initialized
2022-10-18 14:08:57.975 GMT [185] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2022-10-18 14:08:57.975 GMT [185] LOG:  listening on IPv6 address "::", port 5432
2022-10-18 14:08:57.998 GMT [185] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-10-18 14:08:58.510 GMT [185] LOG:  redirecting log output to logging collector process
2022-10-18 14:08:58.510 GMT [185] HINT:  Future log output will appear in directory "/opt/bitnami/postgresql/logs".
2022-10-18 14:08:58.514 GMT [187] LOG:  database system was shut down in recovery at 2022-10-18 14:08:57 GMT
2022-10-18 14:08:58.515 GMT [187] LOG:  entering standby mode
2022-10-18 14:08:58.528 GMT [187] LOG:  redo starts at 0/A8274388
2022-10-18 14:08:58.528 GMT [187] LOG:  consistent recovery state reached at 0/A8274468
2022-10-18 14:08:58.529 GMT [187] LOG:  invalid record length at 0/A8274468: wanted 24, got 0
2022-10-18 14:08:58.529 GMT [185] LOG:  database system is ready to accept read only connections
2022-10-18 14:08:58.537 GMT [191] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
2022-10-18 14:08:58.543 GMT [192] FATAL:  could not connect to the primary server: could not translate host name "postgresha-postgresql-ha-postgresql-2.postgresha-postgresql-ha-postgresql-headless.harbor-test.svc.cluster.local" to address: Name or service not known
 done
server started
postgresql-repmgr 14:08:58.57 INFO  ==> ** Starting repmgrd **
[2022-10-18 14:08:58] [NOTICE] repmgrd (repmgrd 5.3) starting up
[2022-10-18 14:08:58] [ERROR] an older version of the "repmgr" extension is installed
[2022-10-18 14:08:58] [DETAIL] extension version 5.2 is installed but newer version 5.3 is available
[2022-10-18 14:08:58] [HINT] verify the repmgr installation is updated properly before continuing

Oct 18 '22 14:10 pascalrimann

@rafariossaa is there any way to reopen this issue? we still have the problem

Oct 26 '22 10:10 pascalrimann

charts charts copied to clipboard

Postgres-HA not able to upgrade 8.0.0

Name and Version

What steps will reproduce the bug?

Are you using any custom parameters or values?

What is the expected behavior?

What do you see instead?

Additional information

charts
charts copied to clipboard