During the offline upgrade of the VMware Skyline Health Diagnostics appliance, customers copy the VMware-shd-patch-offline-4.0.10-<build>.tar.gz patch bundle.
After extracting the bundle and running ./stageupdate, the SHD Appliance reboots and begins installing the patches sequentially one after the other.
Customers can notice the update process may hang—showing an intermediate SHD version post-reboot while the Upgrade History Summary still indicates “Stage Update” in progress. This stall occurs only after the prescribed steps above and `./stageupdate` commands have been run exactly as documented.
SHD version 4.0.X upgrade scenario
During the offline upgrade process, the system creates backup files before applying each patch to ensure recovery capability. The backup creation process uses high CPU resources due to file compression operations, which can overwhelm appliances with limited processing power. This causes the entire upgrade process to hang while the system struggles to complete the backup task, preventing the upgrade from progressing to the next patch level.
rm /opt/vmware-shd/vmware-shd/updates/upgrade.lock
./stageupdate
- Take the backup before you attempt the upgrade.
- The lock file prevents concurrent or repeated stage updates. Removing it forces the process to restart at the next pending patch.
- Always verify appliance health and service status after each successful patch.