If some of you are using a standalone version of Orchestrator, you may experience a similar issue during the upgrade. Let's check it out.
The Situation
I attempted to upgrade a few instances of standalone VCF Orchestrator 9.0.1 to 9.0.2. Unfortunately, during the upgrade process, some of the instances encountered an unexpected error.
I spent some time trying to find a reason for such an error in the logs or in the release, but unfortunately, I couldn’t find anything.
The Solution
The only working solution, which did work for me.
Redeploy
- Clean the current deployment:
/opt/scripts/deploy.sh --onlyClean - Reboot the appliance.
- Power it on and wait a few minutes until all services start.
- Deploy the current version of Orchestrator:
/opt/scripts/deploy.sh - Confirm the Orchestrator is up and running.
Upgrade
- Clean the current deployment:
/opt/scripts/deploy.sh --onlyClean - Shutdown the appliance.
- Make a snapshot.
- Power it on and wait a few minutes until all services start.
- Deploy the current version of Orchestrator:
/opt/scripts/deploy.sh - Confirm the Orchestrator is up and running.
- Upgrade using the standard upgrade procedure from here.
The Summary
As in most cases, it’s always recommended to have a clear environment before an upgrade, and this is another example of it.
💡
Would you consider referring this post to a friend if you enjoy my job? Your support helps me to grow and brings more aspiring mates into the community.
I also want to hear from you about how I can improve my topics! Please leave a comment with the following:
- Topics you're interested in for future editions
- Your favorite part or take away from this one
I'll do my best to read and respond to every single comment!
I also want to hear from you about how I can improve my topics! Please leave a comment with the following:
- Topics you're interested in for future editions
- Your favorite part or take away from this one
I'll do my best to read and respond to every single comment!
