"The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 15.4."

[cunnie]

Summary

When using helm to upgrade from 7.11.0 to 7.11.2, my postgresl container wouldn't start.

Steps to reproduce

helm repo update
helm upgrade ci concourse/concourse \
  -f concourse-values.yml \
  --set secrets.githubClientSecret=$(lpass show --note deployments.yml | yq e .github_concourse_nono_auth_client_secret -) \
  --set secrets.hostKey="$(lpass show --note deployments.yml | yq e .tsa_host_key.private_key -)" \
  --set secrets.hostKeyPub="ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDrchtcCq6WFbl2xlWaKQP1UIUDUPPjKrndtrPXFArPs4+zOn5RcGf4zpO2GUD8fZl+8tikG7b+YQTfyOB08zeuA+WqpBVmiaXyK7OJhzuEWwqa60p5Ni1SyNRtcgntY8DLkKnWqzhDaVT/FcXIbnDfyMCDxp7Gs023jha3IGKeIIhRsOkJDcsfByxF63GP70WEs49JNToDCC3CIo8JEGXunjF1matILpJhupsa3obMOk2OCGNI9nleiRfSjE51f9hzYAa1wKqCoBbgOtVQ3mz59yxTFobVZFBP6fZX2GWXaLWHPPiAUtMhiL87pHsa43K0iiV6Yk59yoZ67mOdachp [email protected]" \
  --set secrets.workerKey="$(lpass show --note deployments.yml | yq e .worker_key.private_key -)" \
  --set secrets.workerKeyPub="ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0SIrGT+qIE7w8i67B/YDCfHINEU0LUP67SesaPaesq26rb/HHckPvBfRj+gCxKMvmTipUIVaQLBZlsPEMb+1V8xJBs2s4+9MU6QG6i7CEYTWyYlhVSDxU4HtwxGGnW9c5lASBB1jPkx2gWv0kgQYXQfrcbXSJ4fUtgdo0ZtePnXV7Qd30YUoR2fcuqEdAGg0S317V54vgeD2tfL04Qwhyu2Hbz4ZwTyhNe1YNcKET6v8ttRjVOIfMe+FF+JHqGJUiu5jygJ2p+29sm50JHEuxK+HjYpajmW8BRmXK7fIvDX24RDIs9ACZ+s+asEU8yEKkmdnFB5kUAukQWRuqUWYd [email protected]" \
  --set secrets.sessionSigningKey="$(lpass show --note deployments.yml | yq e .worker_key.private_key -)" \
  --set secrets.vaultAuthParam="$(lpass show --note deployments.yml | yq e .vault_client_auth_param -)" \
  --wait

Expected results

Success!

Actual results

Error: UPGRADE FAILED: timed out waiting for the condition

Additional context

kubectl logs ci-postgresql-0 -c postgresql
postgresql 18:27:05.10
postgresql 18:27:05.11 Welcome to the Bitnami postgresql container
postgresql 18:27:05.11 Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 18:27:05.11 Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 18:27:05.11
postgresql 18:27:05.14 INFO  ==> ** Starting PostgreSQL setup **
postgresql 18:27:05.16 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 18:27:05.17 INFO  ==> Loading custom pre-init scripts...
postgresql 18:27:05.18 INFO  ==> Initializing PostgreSQL database...
postgresql 18:27:05.20 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 18:27:05.21 INFO  ==> Generating local authentication configuration
postgresql 18:27:05.23 INFO  ==> Deploying PostgreSQL with persisted data...
postgresql 18:27:05.25 INFO  ==> Configuring replication parameters
postgresql 18:27:05.30 INFO  ==> Configuring fsync
postgresql 18:27:05.31 INFO  ==> Configuring synchronous_replication
postgresql 18:27:05.37 INFO  ==> Loading custom scripts...
postgresql 18:27:05.38 INFO  ==> Enabling remote connections
postgresql 18:27:05.39 INFO  ==> ** PostgreSQL setup finished! **

postgresql 18:27:05.42 INFO  ==> ** Starting PostgreSQL **
2024-02-08 18:27:05.446 GMT [1] FATAL:  database files are incompatible with server
2024-02-08 18:27:05.446 GMT [1] DETAIL:  The data directory was initialized by PostgreSQL version 14, which is not compatible with this version 15.4.

Triaging info

• Concourse version: 7.11.0, 7.11.2
• Browser (if applicable):
• Did this used to work? not this particular upgrade, no.

[taylorsilva]

This sounds like an issue with the chart. Which chart version were you on?

Also, we don't recommend using the postgres bundled with the chart. It's there purely so folks can test out the chart without having to think about the db stuff. If you're running a long-term Concourse cluster, we recommend having the db managed externally to the concourse chart.