OVF Tool deployment fails with 'Unsupported value'
search cancel

OVF Tool deployment fails with 'Unsupported value'

book

Article ID: 432820

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • When attempting to deploy an OVF using the OVF Tool, the deployment fails with the following errors and warnings:
Error: OVF Package is not supported by target:
- Line -1: Unsupported value 'XXXXX' for attribute 'key' on element 'ExtraConfig'.
Warning:
- No manifest file found.
  • Manual deployment of the same vApp via the VCD UI succeeds without error.

Environment

10.x

Cause

The OVF Tool enforces strict validation of the OVF descriptor file by default prior to deployment. The presence of advanced `ExtraConfig` parameters (such as `numa.nodeAffinity`) and the absence of a manifest (`.mf`) file cause the validation checks to fail, blocking the deployment. The VCD UI deployment process implicitly handles or bypasses these client-side validation constraints.

Resolution

  1. Modify the OVF Tool deployment command to bypass the strict validation checks.
  2. Append the `--allowExtraConfig` flag to permit advanced configuration parameters within the OVF descriptor.
  3. Append the `--skipManifestCheck` flag to bypass the validation of the missing manifest file.

    Example command:
    `ovftool --allowExtraConfig --skipManifestCheck <source_path> <target_locator>`

Additional Information

OVF Tool Command-Line Options