NVIDIA daemon vib does not populate in additional components when NVIDIA AIE and Daemon VIBs are pushed through Custom Depot

Products

• VMware vCenter Server

Issue/Introduction

In vSphere Lifecycle Manager (vLCM), when a Custom depot is configured to include NVIDIA AIE and Daemon VIBs via custom URLs, initiating a 'Sync updates' task triggers an unintended behavior.

The synchronization process causes the Daemon component (nvd-gpu-mgmt-daemon...) to be unexpectedly removed from the Image Depot inventory.

Cause

Both the nvd-gpu-mgmt-daemon and NVD-AIE-800 components are configured with the generic filename metadata.zip in their respective XML definitions.

nvd-gpu-mgmt-daemon_580.65.05-0.0.0000
<metaList>
  <metadata>
    <productId>embeddedEsx</productId>
    <version>7.0.0</version>
    <locale/>
    <url>metadata.zip</url>
    <channelName>default</channelName>
  </metadata>
</metaList>

NVD-AIE-800_580.65.05-1OEM.800.1.0.20613240
<metaList>
  <metadata>
    <productId>embeddedEsx</productId>
    <version>8.0.0</version>
    <locale/>
    <url>metadata.zip</url>
    <channelName>default</channelName>
  </metadata>
</metaList>

During the synchronization operation, this naming conflict causes the system to replace the existing metadata file with the subsequent download, effectively corrupting the depot inventory for the overwritten component.

Resolution

To resolve the file name collision issue, import the NVIDIA bundles as Offline Depots instead of configuring them via Custom Depot URLs.

Procedure:

1. Download the offline bundle .zip files for both the NVIDIA AIE and Daemon components.
2. Navigate to vSphere Lifecycle Manager > Image Depot.
3. Select Actions > Import Updates.
4. Upload the downloaded bundles manually.