VUM error during remediation of ESXi host upgrade from 5.1 to 5.5:
"vmware update manager 5.5 Cannot run upgrade script on host"
Debugging the problem:
Troubleshooting this problem led to a few discoveries online of users experiencing the same error message but different log entries regarding problem. This can be read in kb articles below:
I tried with the VMware rollup ESXi as well as the Dell provided iso and had the exact same problem.
After the upgrade fails, SSH to your ESXi host and look for the following entries in \var\log\vua.log
2013-12-29T19:10:51.102Z [FFE898C0 info 'VUA'] VUA exiting
2013-12-29T19:10:51.104Z [FFE898C0 error 'Default'] Alert:WARNING: This application is not using QuickExit(). The exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp:147
--> backtrace rip 1a8272a3 Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace rip 1a64e6e9 Vmacore::System::SystemFactoryImpl::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace rip 1a5d082f Vmacore::Service::Alert(char const*, char const*, int)
--> backtrace rip 1a60f0e8 Vmacore::Service::AppImpl::Init(Vmacore::Service::Config*)::do_quick_exit::invoke()
--> backtrace rip 1ae68ed9 /lib/libc.so.6(exit+0xe9) [0x1ae68ed9]
--> backtrace rip 1ae52f04 /lib/libc.so.6(__libc_start_main+0xe4) [0x1ae52f04]
--> backtrace rip 0804e5e1 /usr/share/vua/vua [0x804e5e1]
I opened a case with VMware to get this resolved so if you experience the same problem I do recommend contacting VMware support to further assist. If you intend to use this fix, please do so at your own risk.
To fix this issue, manually remove the FDM agent on the host, reboot and retry the upgrade.
Note: Removing the host from a vSphere HA cluster also removes the agent. If the agent is not removed, you may have to manually remove the agent.
To manually remove the FDM agent from the host, run these commands:
cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
Reboot the host
After the FDM agent is removed and host has been rebooted you can run the remediation again for host upgrade.