-
Notifications
You must be signed in to change notification settings - Fork 656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed on upgrading BOSH Director from v271.2.0 to v280.0.14 #2490
Comments
It seems like you are upgrading from an ancient version of Postgres. This issue was fixed here: cloudfoundry/bpm-release#152 |
Thank you so much for the response @rkoster! Indeed we're operating an "outdated" BOSH environment and have not done the upgrade regularly as we should. We have seen this issue intermittently on a few runs of BOSH Director upgrade testing. How can we move forward with this BOSH Director v280.0.14 upgrade and ensure that this issue won't happen in our existing production BOSH environments? Option 1: Can we first manually shut down Postgres 10 on the BOSH Director VM before attempting BOSH Director upgrade? If yes, which command sequences should be used to properly shut down Postgres 10 and other BOSH Director related services? Option 2: First update BPM component to v1.1.14 or higher (cloudfoundry/bpm-release#152 (comment)) with the fix on current BOSH Director v271.2.0 before upgrading to BOSH Director v280.0.14. Any other options? Greatly appreciate your suggestions here. |
Updating BPM would still be an update of the instance, and as such have a change of an improper Postgres shutdown. @bgandon do you remember if there was a workaround that was used before the fix was implemented? |
Hi @bgandon, We're thinking of using the Option 1 as a workaround for manually shutting down Postgres 10 on the BOSH Director VM before attempting BOSH Director upgrade. Please help to confirm if the following steps will work.
|
Describe the bug
Failed on upgrading BOSH Director from v271.2.0 to v280.0.14
To Reproduce
Steps to reproduce the behavior (example):
Deploy a bosh director v271.2.0 on vSphere:
Upload stemcell ubuntu-bionic 1.92
Deploy cf-deployment 21.5.0.
Upgrade the current bosh director v271.2.0 to v280.0.14
The pre-start script of the postgres job failed.
Expected behavior
BOSH Director should be successfully upgraded from v271.2.0 to v280.0.14
Logs
When sshing into the BOSH Director VM, I found this error in /var/vcap/sys/log/postgres/pre-start.stdout.log:
When BOSH Director is migrating the database from Postgres 10 to Postgres 15 during the upgrade, it's complaining about the source database (Postgres 10?) is not shutdown cleanly. I attempted to rerun the BOSH Director upgrade several times, but it did not help.
Versions (please complete the following information):
$ bosh -v
version 6.1.1-a0c78bc2-2019-10-25T22:16:25Z
Succeeded
ubuntu-bionic/1.92 for current BOSH Director v271.2.0
ubuntu-jammy/1.340 for new BOSH Director v280.0.14
Deployment info:
We're using "bosh create-env" command with bosh-deployment to create and upgrade BOSH Director environment.
BOSH Director creation script:
new bosh-deployment: https://github.com/cloudfoundry/bosh-deployment/tree/15cbd254db78ab49ef957f2d80ffd2901b09d6e5
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: