(CO) Support Tip: How to tell if CO Virtual Appliance was updated properly?
Hello CO Community,
There have been a number of individuals that have upgraded or updated their CO Virtual Appliances using the Standalone Installer (TAR) rather than the Virtual Appliance binaries (ISO or ZIP).
For those that do not know, using the standalone installer (TAR) to upgrade the Virtual Appliance is not supported. The standalone installer does not include all of the necessary binaries to upgrade the Virtual Appliance properly. A previous CO Support Tip was provided in August 2017 about this issue.
(CO) Support Tip: Updating CO Virtual Appliance using Installer is unsupported.
While this is encountered occasionally, how do you identify when the installer (tar) is used to update a virtual appliance?
This is where the Status_Report.txt file generated by the PVTK 2.0 Utility (pvsupport.sh -status or pvsupport.sh -grab) will help.
Within the first few lines of this information is included the CO version and the Vami manifest, which includes the version information. If these two versions are different, then this issue exists.
Date: Wed Feb 7 16:20:09 EST 2018
Hostname: <CO Server Hostname>
OS: CentOS release 6.5 (Final)
Uptime: 16:20:09 up 72 days, 6:31, 5 users, load average: 2.20, 1.38, 1.08
CO version: HPE Cloud Optimizer Version: 03.01.131 (Appliance)
Vami manifest: 03.00.152.00
CO HF (last): CO_3.01.131_HF_VCENTER_6
Tomcat version: HPOvTomcatB-7.00.072-1.x86_64
DB version: vertica-7.1.1-0.x86_64
OA version: 12.02.008
Please see knowledge document for more information and examples.
KM03109063 - How do you determine if Cloud Optimizer Virtual Appliance was updated using Standalone Installer?
It is recommended to upgrade to the next higher release using the ISO or ZIP to correct this issue.
I hope that this information is helpful.
Have a great weekend!
Micro Focus SW Support Engineer