Standalone VCF Orchestrator Upgrade Issue to 9.0.2

ByEditor

If you are using a standalone version of Orchestrator, you might encounter a similar issue during the upgrade. Let’s take a look.

The Situation

Read moreHow to Use WordPress Contextual Help to Improve UX (5 Steps)

I tried upgrading several standalone VCF Orchestrator 9.0.1 instances to 9.0.2. Unfortunately, during the upgrade, some instances faced an unexpected error.

I spent time looking for the error cause in the logs or release notes but found nothing.

The Solution

Read more23 WordPress Development Resources to Advance Your Skills (2021)

The only working solution that succeeded for me.

Redeploy

  1. Clean the current deployment: /opt/scripts/deploy.sh --onlyClean
  2. Reboot the appliance.
  3. Power it on and wait a few minutes until all services start.
  4. Deploy the current version of Orchestrator: /opt/scripts/deploy.sh
  5. Confirm the Orchestrator is up and running.

Upgrade

  1. Clean the current deployment: /opt/scripts/deploy.sh --onlyClean
  2. Shutdown the appliance.
  3. Make a snapshot.
  4. Power it on and wait a few minutes until all services start.
  5. Deploy the current version of Orchestrator: /opt/scripts/deploy.sh
  6. Confirm the Orchestrator is up and running.
  7. Upgrade using the standard upgrade procedure from here.

The Summary

As usual, it’s advisable to have a clean environment before an upgrade, and this is another example.

💡

Would you consider sharing this post with a friend if you find my work helpful? Your support helps me grow and brings more aspiring members into the community.
I also want your feedback on how I can improve my topics! Please leave a comment with:
– Topics you’re interested in for future editions
– Your favorite part or takeaway from this one

I’ll do my best to read and respond to every single comment!

Similar Posts