Service Engine creation fails with 500 response code from vCenter

Products

• VMware Avi Load Balancer

Issue/Introduction

When attempting to create a new Service Engine (SE) on the Avi Controller, the deployment fails with 500 response code from vCenter. Users may observe a "CREATE_SE_FAIL" in Operations -> Evenets -> All Events on the Avi UI.

 

Environment

vCenter Cloud

Cause

This issue typically occurs due to metadata corruption or a mismatch within the vCenter Content Library. While the Content Library entry for the Service Engine OVA exists in the vCenter database, the actual underlying files (the storage backing) are missing or inaccessible.

When the Avi Controller requests the Content Library to deploy the SE, vCenter returns a 500 error because it cannot locate the physical files associated with the library item ID.

To confirm this specific issue, review the following logs:

• Avi Controller (/opt/avi/log/cc_agent_<cloud_name>.log): Look for a 500 status code during an OVF filter action:

  vcenterlib/veenter_se_lifecycle.go:1609 [<vcenter_IP>] 'POST' request to API 'https://<vcenter_fqdn>/rest/com/vmware/vcenter/ovf/library-item/id:<image_id>?-action=filter': Status: "": Code: '500'

   

  
  
  
  

• vCenter Event Logs: Search for errors regarding "storage backing" or missing library items:

  A general system error occurred: The export of library item [ID] has failed. Reason: Cannot find library item [SE_Image_Name] in the storage backing of library [Library_Name].

  >


Resolution

To resolve this, you must force the Avi Controller to re-upload a clean version of the SE image to the vCenter Content Library.

1. Log in to the vSphere Client.

2. Navigate to Content Libraries: Go to Menu > Content Libraries.

3. Identify the Library: Select the specific Content Library configured in your Avi Controller's vCenter Cloud settings.

4. Delete the Corrupt Image:

   • Click on the Templates or Other Types tab.

   • Locate the Service Engine OVA/Template causing the error (matching the version in the logs).

   • Right-click the item and select Delete.

5. Trigger Re-upload:

   • Return to the Avi Controller UI.

   • The Controller will detect the missing image and automatically begin pushing a fresh OVA to the Content Library during the next deployment attempt.

6. Verify & Retry: Once the upload status in vCenter shows as complete, re-attempt the Service Engine creation.