Deployment Failure of OVA/OVF Library Items on vSAN ESA Using vRealize Automation

Products

• VMware Aria Suite
• VMware vCenter Server
• VMware vSAN

Issue/Introduction

Symptoms:

• Deployment of VMs, VMs from template, and OVA/OVF library items on vSAN Express Storage Architecture (ESA) fails during the reconfigure step.
• The vCenter Server vpxd.log displays SOAP request failures with HTTP 500 (Internal Server Error) during OVF/OVA deployment.
• The vCenter Server vpxd.log also displays errors related to VmotionTracker - Datastore not found
• The vpxd service crashes, producing core.vpxd-worker.xxxxxxx files in the /var/core directory

Here are examples of each type of log message you might encounter:

SOAP Request Failures with HTTP 500 (Internal Server Error)

1. Warning about SOAP request failure due to an internal server error:

   YYYY-MM-DDTHH:MM:SS.SSSZ warning vpxd[xxxxxx] [Originator@xxxx sub=vmomi.soapStub[xxx] opID=xxxxxxxx-xx] SOAP request returned HTTP failure; <<io_obj p:0xXXXXXXXXXXX, h:xxx, <TCP '127.0.0.1 : xxxx'>, <TCP '127.0.0.1 : xxxx'>>, /vsm/ovfConsumer/>, method: selectCapabilities; code: 500(Internal Server Error)

2. Warning about SOAP request failure during the cloning process:

   YYYY-MM-DDTHH:MM:SS.SSSZ warning vpxd[xxxxxx] [Originator@xxxx sub=vmomi.soapStub[xxx] opID=xxxxxxxx-xx] SOAP request returned HTTP failure; <<io_obj p:0xXXXXXXXXXXX, h:xxx, <TCP '127.0.0.1 : xxxx'>, <TCP '127.0.0.1 : xxxx'>>, /vsm/ovfConsumer/>, method: cloneEntities; code: 500(Internal Server Error)

VmotionTracker - Datastore Not Found Error

3. Error indicating a missing datastore during a VMotion operation:

   2024-01-08T08:58:35.271Z error vpxd[1831578] [Originator@6876 sub=drsExec opID=44a1bfd5-01] VmotionTracker - Datastore vim.Datastore:datastore-1112 not found

Failed to Invoke OVF Stub Adapter

4. Information message about failing to invoke the OVF stub adapter and retrying after login:

   2024-01-08T11:59:46.281Z info vpxd[1115107] [Originator@6876 sub=OvfConsumers opID=2

Environment

VMware vSAN 8.0.x
VMware vCenter Server 8.0.2
VMware vRealize Automation 8.x

Cause

When the vSphere system tries find a unique identifier for the data files it can't find it. This missing information causes the system to stop the setup process because it can't confirm that the data files are correctly linked to the virtual machine.

This missing information causes errors and stops the virtual machines from being set up correctly on the vSAN ESA storage setup.

Resolution

This issue is resolved in vCenter 8.0U3 -24022515 version.