Upgrading ESXi though SDDC Manager may fail when vSphere Replication Appliance is deployed
search cancel

Upgrading ESXi though SDDC Manager may fail when vSphere Replication Appliance is deployed

book

Article ID: 324133

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware Live Recovery VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Upgrade of ESXI hosts on VI domains via VUM bundle failed with "Failure during VUM remediation" error.
  • Entries similar to the below are seen on the vCenter Server in/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log:
[2020-08-26 10:36:03:855 'SingleHostRemediate' 140481384240896 ERROR]  [hostUpdateBase, 790] VimFault: Another task is already in progress.
[2020-08-26 10:36:03:858 'SingleHostRemediate' 140481384240896 ERROR]  [hostUpdateBase, 790] [backtrace begin] product: VMware Update Manager, version: 7.0.1, build: build-16617338, tag: vmware-vum-server, cpu: x86_64, os: linux, buildType: release backtrace[00] libvmacore.so[0x002EAE12] backtrace[01] libvmacore.so[0x0019D949]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int) backtrace[02] libvmacore.so[0x0018F573]: Vmacore::System::SystemFactory::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&) backtrace[03] libvci-vcIntegrity.so[0x007505EB]: Integrity::HostUpdate::HostUpdateBase::WaitTaskCompletion(Vmacore::Ref<Vmomi::Any>&) backtrace[04] libvci-vcIntegrity.so[0x00768132]: Integrity::HostUpdate::RemediateHost::InstallUpdateV2(std::vector<std::string, std::allocator<std::string> >, std::vector<std::string, std::allocator<std::string> >&, int, int, bool, std::string&) backtrace[05] libvci-vcIntegrity.so[0x0081C1C0]: Integrity::HostUpdate20::InstallerImpl::Install20(std::string const&, std::vector<std::string, std::allocator<std::string> >&, std::vector<std::string, std::allocator<std::string> >&, std::string&) backtrace[06] libvci-vcIntegrity.so[0x007CB843]: Integrity::HostUpdate20::Installer20::Install(std::vector<std::string, std::allocator<std::string> >&, std::string&) backtrace[07] libvci-vcIntegrity.so[0x007BCC5A]: Integrity::HostUpdate20::InstallController::InstallUpdate(std::vector<std::string, std::allocator<std::string> >&, bool, std::string&) backtrace[08] libvci-vcIntegrity.so[0x007C2AC4]: Integrity::HostUpdate20::InstallController::Install(std::vector<std::string, std::allocator<std::string> >&) backtrace[09] libvci-vcIntegrity.so[0x00416BE4]: Integrity::SingleHostRemediateTask::RemediateSingleHostV2(Vmacore::Ref<Vmomi::MoRef>) backtrace[10] libvci-vcIntegrity.so[0x004177F1]: Integrity::SingleHostRemediateTask::DoRun() backtrace[11] libvci-vcIntegrity.so[0x0035E10C]: Integrity::VciTaskBase::Run() backtrace[12] libvmacore.so[0x0022B102] backtrace[13] libvmacore.so[0x00230760] backtrace[14] libvmacore.so[0x002A9A28] backtrace[15] libpthread.so.0[0x00007F87] backtrace[16] libc.so.6[0x000F35BF] backtrace[17] (no module) [backtrace end]


Environment

VMware vSphere Replication 8.x
VMware Cloud Foundation 4.1

Cause

This issue occurs due to the replication appliance pushing its VIBs which generates the error "Another task is in progress"

Resolution

This is a known issue in VMware Cloud Foundation 4.1 where vSphere Replication is also installed.

Workaround:
  1. Take a backup, or snapshot, of the vSphere Replication Appliance before proceeding.
  2. SSH to the vSphere Replication Appliance using the root user.
  3. Update HMS properties to disable auto-update of HMS vibs and restart hms service, by run the following commands:
/opt/vmware/hms/bin/hms-configtool -cmd reconfig -property hms-auto-install-hbragent-vib=false
service hms restart
  1. Navigate to the SDDC Manager UI and restart the ESXi upgrade.
  2. Once the upgrade has completed, update HMS properties to re-enable auto-update of HMS vibs and restart hms service:
/opt/vmware/hms/bin/hms-configtool -cmd reconfig -property hms-auto-install-hbragent-vib=true
service hms restart


Powered by Wolken Software