Upgrading vRO fails at deactivating the cluster precisely at cluster leave operation 
search cancel

Upgrading vRO fails at deactivating the cluster precisely at cluster leave operation 

book

Article ID: 345985

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

  • To upgrade the vRO appliance.


Symptoms:
  • Upgrading vRO fails at deactivating the cluster precisely at cluster leave operation
  • checking the journalctl logs it complains that the command failed as DNS resolution did not work


Environment

VMware vRealize Orchestrator 8.x

Cause

  • The environment was initially installed using a short name instead of FQDN as hostname, something that is not supported and is breaking the upgrade.

Resolution

  • There is a workaround.


Workaround:
  • Workaround steps below :

 

  1. Change the hostname back to FQDN: hostnamectl set-hostname <FQDN>
  2. Open /etc/current_node for edit and replace the short name with the FQDN
  3. Run: /opt/health/run-once.sh health and make sure there are no errors reported
  4. Run: vracli cluster leave (wait for it's completion)
  5. Remove the certs: rm /data/vco/usr/lib/vco/app-server/conf/security/jssecacerts
  6. Run the deploy script: /opt/scripts/deploy.sh
  7. Create a new pre-upgrade snapshot
  8. Trigger the upgrade again

 


Additional Information

Impact/Risks:
  • vRO upgrade will fail.


Powered by Wolken Software