Closed rkoster closed 5 years ago
From bosh director 268.3.0 release notes
**If your director is using Postgres 9, do not upgrade to 10.6 at this time**
We should not be affected since the postgres-release is responsible for the db upgrade. So as long as the director is able to communicate with an 11.1 db we are fine.
Currently credhub bbr is broken in our pipeline:
+ SDK_PATH=/var/vcap/jobs/database-backup-restorer
+ BBR_ARTIFACT_FILE_PATH=/var/vcap/store/bbr-backup/bbr-credhubdb//credhubdb_dump
+ CONFIG_PATH=/var/vcap/jobs/bbr-credhubdb/config/bbr.json
+ /var/vcap/jobs/database-backup-restorer/bin/backup --config /var/vcap/jobs/bbr-credhubdb/config/bbr.json --artifact-file /var/vcap/store/bbr-backup/bbr-credhubdb//credhubdb_dump
2018/12/10 10:17:56 Unable to check version of Postgres: could not parse semver: "11.1" - exit code 1error 4:
Error attempting to run backup for job bbr-uaadb on bosh/0: 2018/12/10 10:17:56 Unable to check version of Postgres: could not parse semver: "11.1" - exit code 1
A long term solution, for this is switching to the bbr-postgres-db
job from the postgres-release.
bbr-postgres-db
job currently relies on bosh links which don't work with bosh create-env
have created a PR to fix it: https://github.com/cloudfoundry/postgres-release/pull/46
When using bbr-postgres-db
we also no longer need the bosh-backup-and-restore-sdk
packages which we are tracking het bucc-bbr-boshrelease
. Have removed them in v8: https://github.com/starkandwayne/bucc-bbr-boshrelease
Required bbr changes already in develop: https://github.com/starkandwayne/bucc/commit/8278634a4ee45e032463128f1cfe3187a1b6c09d
Now we just have to wait for the postgres-release
PR to be merged, and picked up by our ci.
Latest postgres release has updated to 11.1 from 9.x this issue is used for tracking upgrade issues we might encounter.