VMware vRealize Orchestrator Automates Complex IT Processes and simplify the automation of complex IT tasks, which integrates with vRealize Suite to further improve service delivery efficiency, operational management and IT agility.
It is suggested to upgrade vRO and then vRA one by one in a same day. Follow my previous blog for vRA upgrade.
- Take an offline snapshot of the virtual appliances.
- Keep a cold clone copy of the virtual appliances (optional)
- Ensure there is a most recent successful image level backup available for the virtual appliances.
- Backups for vRealize Appliance configuration files in the following directories for each appliances.
- /opt/vmware/etc/lighttpd/ (optional)
- /opt/vmware/etc/vami/ (optional)
- /opt/vmware/sbin/vami-lighttpd/ (optional)
- /opt/vmware/sbin/vami-sfcbd/ (optional)
- Note down all the SSL certificate details and their source server details as well.
- We must export the configuration from vRO configurator portal before upgrade.
- Backups for all the databases.
- Backups for any other configuration files you have customized.
- Perform the upgrade for each appliance at a time when the system has an approved downtime.
- If the root password is 365 days old or less, we must change the password before we run the upgrade. (#chage –l)
Procedure to Stop the Following Services:
Package Download Procedure:
Download the update ISO file from the VMware site.
Connect the CD-ROM drive for the virtual appliance you are updating to the ISO file you downloaded.
Go to the management console for your vRO virtual appliance by using its fully qualified domain name "https://myvro.lab.com:5480"
Log in with the user name root, Click the Update tab, Click Settings, Under Update Repository, select Use CDROM Updates, Click Save Settings
Prerequisites for upgrading vRealize Orchestrator Appliance:
If your deployment uses a load-balancer, disable one vRO Appliance for load-balancer traffic. The first appliance you plan to upgrade must be connected to the load-balancer.
Before you trigger the upgrade for the appliance that use load balancers, disable traffic for all nodes except the first node that you plan to upgrade in order to prevent cache errors.
All other instances of vRO Appliance must be disabled for load balancer traffic when you upgrade them.
If you are using a vRO Appliance as a dedicated appliance database server, update it before you update a vRO Appliance used as an application server.
Verify that the identity server (SSO) is running.
Login to VAMI by using its fully qualified domain name "https://myvro.lab.com:5480" then Click on the Update tab, Click Status, Click Check Updates, Click on Details, Click on Install Updates, Click on OK and then reboot the virtual appliance.
If the deployment uses a load balancer, repeat these steps for each vRO Appliance. Leave the second and subsequent vRO Appliance disabled for load balance traffic when you apply the update.
Reconnect all vRO appliances to the load balancer.
Login to VAMI and check if all services are registered now.
Once the vRO appliance got reboot then wait for 10-15 minutes.
After finishing an upgrade in a high availability deployment, you must configure the load balancer to pass traffic on port 8444 to the vRO Appliance to support remote console features.
Post Upgrade Tasks for vRealize Orchestrator:
SSH to vRO appliance and check if all of their services are running.
Login to vRO appliance by using vRO client and check if any error it has.
Login to the vRO configurator and check if all the plugins and services has any error.
Check all the databases if it has any errors like vRO postgresql.
Verify that the Orchestrator Appliance “vco” user account has sufficient permissions for all custom files and folders.
Check if all SSL certificates are in place else Import the SSL certificates for each vCenter Server instance that you defined.
Check the vRO configurator for all the tabs for any errors.
Check all the vRO log files in case of any error.
Login to vRA VAMI and check if all the services are registered.
Ensure all vRealize portals are accessible without any error.
Monitor the health of vRealize environment for some time, post upgrade.
Most Expected Resolved Issues in vRO 6.0.5:
Changing a log level from Orchestrator Configurator does not work.
After upgrading to vRealize Orchestrator 6.0.4, you can no longer connect to a Microsoft SQL Server database over SSL because of JDK 1.8 that is included in version 6.0.4 supports a restricted set of cipher suites compared to earlier versions of JDK.
Denial of service vulnerability in Apache Tomcat (CVE-2016-3092)
Glibc getaddrinfo() stack-based buffer overflow.
System.Data.Services.DataServiceException Resource not found for the segment "VirtualMachines"