In the fdm-installer.log file, located at /var/run/log/, you see entries similar to:
fdm-installer: [9283522] <YYYY-MM-DD><time>: Logging to /var/run/log/fdm-installer.log </time>
fdm-installer: [9283522] <YYYY-MM-DD><time>: extracting vpx-upgrade-installer/VMware-fdm-eesx-2-linux-1750787.tar.gz... </time>
[9283522] <YYYY-MM-DD><time></time>: exec rm -f /tmp/vmware-root/ha-agentmgr/upgrade
[9283522] <YYYY-MM-DD><time></time>: status = 0
[9283522] <YYYY-MM-DD><time></time>: exec cd /tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer
[9283522] <YYYY-MM-DD><time></time>: status = 0
fdm-installer: [9283522] <YYYY-MM-DD><time>: Installing the VIB </time>
fdm-installer: [9283522] <YYYY-MM-DD><time>: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: Installation Result </time>
fdm-installer: Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
fdm-installer: Reboot Required: true
fdm-installer: VIBs Installed: VMware_bootbank_vmware-fdm_5.5.0-1750787
fdm-installer: VIBs Removed:
fdm-installer: VIBs Skipped:
fdm-installer: [9283522] <YYYY-MM-DD><time>: There is a pending reboot. Remove the vib... </time>
[9283522] <YYYY-MM-DD><time>: exec esxcli software vib remove -n=vmware-fdm.vib </time>
[NoMatchError]
No VIB matching VIB search specification 'vmware-fdm.vib'. Please refer to the log file for more details. 20093365] <YYYY-MM-DD><time></time>: status = 1 fdm-installer: [20093365] <YYYY-MM-DD><time></time>: Unable to install HA bundle because a host reboot is required. Reboot host then try again.