Add image form in VCF-A hangs when uploading an OVA with malformed or invalid OVF

Products

• VCF Automation

Issue/Introduction

The form UI located under VCF-A > Build and Deploy > Content Libraries > Add Image does not progress or complete the upload after file selection and submission when the uploaded OVA contains a malformed or schema-invalid OVF descriptor.

The UI will hang with a spinning icon, but no visual indication of an error is presented. The failure is only detectable by reviewing either:

• The browser's developer console (F12 > Console tab), or

• The Content Libraries page, where the task may appear with a failed status.

Observable Symptoms:

• The Add Image form becomes unresponsive or appears stuck after clicking submit.

• No in-form error or notification is shown to the user.

• Browser console logs reveal an error similar to:

   

  ERROR Ye: Malformed OVF at Ke.toXML

• If the OVF fails schema validation, the Content Library > Task Details will show:

   

  Validation failed for the OVF file you provided: Fatal: Line/char 17/22: cvc-complex-type.2.4.a: Invalid content was found starting with element {"http://www.vmware.com/schema/ovf":Description}. One of {"http://schemas.dmtf.org/ovf/envelope/*":Info} is expected.

Environment

VMware Cloud Foundation Automation (VCF-A) 9.x

Cause

This behavior occurs when the user attempts to upload an OVA file that contains a malformed or invalid OVF descriptor. Specifically:

• The OVF fails XML or schema validation.

• The product UI does not currently expose upload-time validation errors inline.

• Backend validation failures are not relayed to the Add Image form in real-time.

As a result, the form appears to “hang” or spin indefinitely, with no visible indication of what caused the failure.

Resolution

VMware is aware of this issue.

There is no immediate resolution within the current UI behavior. However, the following workarounds can assist in diagnosing and confirming the issue:

Workaround 1 – Use Developer Tools

1. Open the browser's developer tools (F12).

2. Navigate to the Console tab.

3. Submit the form and observe any error messages related to OVF, toXML, or schema violations.

   • Example:

      

     ERROR Ye: Malformed OVF at Ke.toXML

Workaround 2 – Check Task Status

1. After form submission, return to:

   • VCF-A > Build & Deploy > Content Libraries

2. Review the associated upload task under Task Details.

3. Look for schema or XML validation errors like:

    

   Validation failed for the OVF file you provided: Fatal: Line/char 17/22: ...

Workaround 3 – Validate OVF Prior to Upload

Validate your OVF file externally before upload using one of the following:

• ovftool (from VMware)

• Online schema validators that support DMTF OVF schema

• Manual review of the XML against the DMTF OVF schema