In my previous post, I discussed how to come out of the checking for updates loop. Sometimes after 3-4 hours the appliance was able to detect the updates and again the installation of updates would take a very long time and fail after couple of hour. Good amount of space was available on all VM partitions.
Here is what I did to fix this issue,
* Before jumping on to the solution, make sure you backup below files
Important: Backup "ovf-env.xml" located at "/opt/vmware/etc/vami", in my case this file was empty after couple of reboots. This file is required while the upgrade process runs post-install scripts.
Don’t forget to take snapshot of VM before starting the upgrade!!!
Time(NTP) is synchronized on all machines.
Uninstall the Vmware tools. As its an Appliance the procedure is different.
1. Take ssh connection to vCAC Server Appliance.
2. Make note of the vmware tools RPMs installed by running the below command
lab-vcac-server:~ # rpm -qa | grep -i vmware-tools
3. Now run the below command to uninstall all vmware-tools RPMs
# zypper remove 'vmware-tools-*'
This command works for all SLES 11 editions.
4. Confirm all the RPM are gone by running the command rpm -qa | grep -i vmware-tools
This will uninstall the vmware tools.
5. Now go ahead and Run the "Check Updates" it would take 20-30 seconds and click on "Install Updates" which would take couple of minutes.
At the final stage of upgrade, the appliance runs the post-upgrade scripts which would look for "ovf-env.xml" which has vCAC Server Appliance's network information, vm description, SSH settings and vsphere port group information. Sometimes after reboot this file goes blank, if that happens it would again fail the upgrade. Make sure you backup this file.
After the successful upgrade, the vmware tools are installed automatically. I hope this post was informative.