VCF Fleet Management fails to detect core component binaries configured via Offline Depot Local Path
search cancel

VCF Fleet Management fails to detect core component binaries configured via Offline Depot Local Path

book

Article ID: 442895

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

VCF Fleet management 9.0.1 does not detect VCF Core Component Binaries version 9.0.2 uploaded to the /data/ directory when the Offline Depot type is configured as Local Path as per the following instructions 

Symptoms include:

  • The Offline Depot type is configured as Local Path.

  • The binary is copied to the /data/ folder.

  • Navigating to Fleet Management > Lifecycle > Binary Management > Patch Binaries does not display the uploaded binary file data in the UI.

  • The following error is observed in /var/log/vrlcm/vmware_vrlcm.log:

    INFO vrlcm[185709] [pool-#-thread-##] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMCOMMON92001', Retry : 'true', Causing Properties : '{ CAUSE ::  }'

com.vmware.vrealize.lcm.common.exception.EngineException: Exception encountered when downloading the binary<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>

, status code : 404

Environment

 

  • VMware Cloud Foundation (VCF) Fleet Management 9.x

  • VMware Cloud Foundation (VCF) Operations 9.x

 

Cause

  • The issue occurs because the VCF Core Component Binaries offline depot contains Express Patch 9.0.2.0100 instead of the required 9.0.2.0 GA release. 
  • Express Patch 9.0.2.0100 cannot be applied directly to version 9.0.1 and requires the environment to be upgraded to 9.0.2.0 first.

Resolution

To resolve this issue, the base GA release must be provided to the Offline Depot:

  1. Download the correct GA version (e.g., 9.0.2.0) of the VCF Core Component Binaries.

  2. Transfer the downloaded binaries to the designated local path folder (e.g., /data/).

  3. Reconfigure the Offline Depot to target the Local Path where the GA binaries were placed.

  4. Navigate to Fleet Management > Lifecycle > Binary Management > Patch Binaries and verify the package details are now displayed in the UI.

Note: The steps to configure the depot for an Express Patch are identical to those for the GA release; however, the GA base version must be detected and applied first.

Powered by Wolken Software