Sunday, December 29, 2013

VUM errror during remediation of ESXi 5.1 to 5.5 host upgade: "Cannot run upgrade script on host" - resolved


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:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007163
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014084



I tried with the VMware rollup ESXi as well as the Dell provided iso and had the exact same problem.

  • VMware-ESXi-5.5-RollupISO.iso
  • VMware-VMvisor-Installer-5.5.0-1331820.x86_64-Dell_Customized_A01.iso


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:
--> backtrace[00] rip 1a8272a3 Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] rip 1a64e6e9 Vmacore::System::SystemFactoryImpl::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] rip 1a5d082f Vmacore::Service::Alert(char const*, char const*, int)
--> backtrace[03] rip 1a60f0e8 Vmacore::Service::AppImpl::Init(Vmacore::Service::Config*)::do_quick_exit::invoke()
--> backtrace[04] rip 1ae68ed9 /lib/libc.so.6(exit+0xe9) [0x1ae68ed9]
--> backtrace[05] rip 1ae52f04 /lib/libc.so.6(__libc_start_main+0xe4) [0x1ae52f04]
--> backtrace[06] rip 0804e5e1 /usr/share/vua/vua [0x804e5e1]

Solution:
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
/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.

8 comments:

  1. Hello, same problem for upgrade esxi 5.0 to 5.1, the fdm uninstall has resolve the problem. thanks

    ReplyDelete
  2. Laurent FleischmannDecember 3, 2014 at 8:06 AM

    Hello, Same problem here for upgrade esxi 5.0 to 5.5 on every host in a cluster (2 HP and 1 Dell). The manual fdm uninstall has resolved it. thanks

    ReplyDelete
  3. This resolved an upgrade from 5.1 to 5.5 on HP DL380p Gen8.

    ReplyDelete
  4. This also solved my problem. I was updating some HS23s from ESXi 5.1 to 5.5 u2 using the IBM customized ISO and this errored out at 28%

    Then tried to use VUM to complete the update but was getting the same error. This fixed it. Thank you.

    ReplyDelete
  5. My situation ..I don't have a HA cluster.Ran to same issue and the VUA log looks the same.
    I created the HA cluster and added the host and performed the upgrade.
    It worked.

    ReplyDelete
  6. Does this work when upgrading from 5.5 to 535 update 3a?

    ReplyDelete