Compute Image Recommendation Task Stuck at 65% After Upgrading vCenter to 9.0

Products

• VMware vCenter Server

Issue/Introduction

• Compute Image Recommendation from vSphere Lifecycle Manager stuck at 65% after upgrading vCenter Server to 9.0. 
  
  
  
  
• On vCenter Server, /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log following log entries are observed : 
  
  

  YYYY-MM-DDTHH:MM:SS error vmware-vum-server[21151] [Originator@6876 sub=Scl::InteropDataMgmt] [InteropDataMgmt 844] CheckGaBuildNumberPresenceInCache:  sourceGaBuildNumber: <Build Number of ESX Host>; displayVersion: <ESX Host Version and Build Number>, 
   in bundle and targetGaBuildNumber: <Build Number of vCenter Server>; displayVersion: <vCenter Server Version and Build Number>, found in bundle. Interop data obtained timestamp: YYYY-MM-DDTHH:MM:SS likely stale. Update required
  YYYY-MM-DDTHH:MM:SS error vmware-vum-server[21151] [Originator@6876 sub=RecommendationEngine::EsxFilter] [esxFilter 271] Failed determining SCL interop compatibilty of source ESX image version: <ESX Host Version and Build Number> with current vc version: <vCenter Server Version and Build Number>. ErrorId: com.vmware.vcIntegrity.lifecycle.scl.InteropBundleUpdateRequired
  YYYY-MM-DDTHH:MM:SS info vmware-vum-server[21151] [Originator@6876 sub=Scl] [Scl 178] VerifyEsxiVcCompatibility called
  YYYY-MM-DDTHH:MM:SS info vmware-vum-server[21151] [Originator@6876 sub=Scl::InteropDataMgmt] [InteropDataMgmt 965] CheckEsxiVcCompatibility for sourceEsxiGaBuildNumber: <Build Number of ESX Host>, version: <ESX host version> with targetVcGaBuildNumber:<Build Number of vCenter Server>, version: <vCenter Server version> is true
  YYYY-MM-DDTHH:MM:SS info vmware-vum-server[21151] [Originator@6876 sub=RecommendationEngine::EsxFilter] [esxFilter 297] Removing candidate version: <ESX Host Version and Build Number> from targetImageCandidates due to nonInteroperability with current VC version

  
  
  

Environment

VMware vCenter Server 9.0

Resolution

1. To workaround the issue, perform a reset of VMware Update Manager database on the vCenter Server by following the steps as outlined in the KB article: Resetting the VMware Update Manager Database
   
   
2. Ensure that the token based URL's within the Lifecycle Manager are readded after performing the reset of Update Manager database. Refer to KB VCF authenticated downloads configuration update instructions to update the necessary systems.
   
   
3. Verify that the Compute Image Recommendation tasks are no longer stuck now.