Creating a Canonical Content Library Fails with an OVF Validation Error
search cancel

Creating a Canonical Content Library Fails with an OVF Validation Error

book

Article ID: 443424

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

When creating a Content Library that subscribes to Canonical content libraries, the library creation completes successfully and displays a status of Ready. However, synchronization of VM Images fails, preventing Ubuntu images from being imported into the Content Library.

The following error may be observed in the UI:

Internal Server Error

Validation failed for the OVF file you provided:
Invalid file: ubuntu-xxxxxx-2#.04-cloudimg.manifest
Invalid file: ubuntu-xxxxxx-2#.04-cloudimg.sbom.spdx
Invalid file: ubuntu-xxxxxx-2#.04-cloudimg.filelist

Here '#' can be any number.

Symptoms:

  1. Log in to the VCF Automation Provider Portal.
  2. Navigate to Infrastructure > Organizations.
  3. Select the target organization.
  4. Under settings, enable Allow this organization to subscribe to Canonical content libraries.
  5. Log in to the VCF Automation Tenant Portal.
  6. Navigate to Build & Deploy > Content Hub > Content Libraries.
  7. Create a new Content Library and select Subscribe to the Canonical library.
  8. The Content Library is created successfully and displays a status of Ready.
  9. VM Images fail to synchronize from the Canonical repository.
  10. The synchronization task reports OVF validation errors similar to the example above.

Environment

VCF Automation 9.1

Cause

This issue is caused by a regression introduced through Canonical's external image publication process. Canonical added Software Bill of Materials (SBOM) files and related metadata files (such as .manifest, .sbom.spdx, and .filelist) to the OVA package and its associated manifest file. However, these files are not referenced within the OVF descriptor and, as a result, are not downloaded during the synchronization process.

After the download completes, the checksum validation mechanism compares the downloaded files against the entries listed in the manifest. Because the newly added metadata files are listed in the manifest but are not present locally, the validation process detects them as missing and fails the OVF validation, causing the image synchronization operation to abort.

Resolution

Broadcom Engineering is aware of this issue and is working on fixing the issue in upcoming releases of VCF Automation.

There is currently no workaround available.

Additional Information