Day 2 Actions Fail Due to VM MoRef ID Sync Issue in VMware Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Day 2 actions fail intermittently in VMware Aria Automation after a virtual machine (VM) restore operation. This article provides the steps to resolve the sync issue caused by changes to the VM MoRef ID.

After performing a VM restore, Aria Automation fails to execute Day 2 actions (e.g., disk resizing). The following error is observed in the /services-logs/prelude/provisioning-service-app/file-logs/provisioning-service-app.log file:

WARN provisioning [host='provisioning-service-app-id' thread='vsphere-enum-60' user='' org='' trace='' parent='' span=''] c.v.p.c.m.a.v.processors.Processor.logUpdateFailure:185 - [Org_Name]:[Env_Name]: Failed updating resource [null]. java.util.concurrent.CompletionException: java.lang.IllegalArgumentException: property 'config.name' not fetched

at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at com.vmware.photon.controller.model.adapters.vsphere.executor.ContextWrapperUtil.lambda$wrapWithOperationContext$0(ContextWrapperUtil.java:24)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.IllegalArgumentException: property 'config.name' not fetched

Environment

VMware Aria Automation 8.18.1 Patch 5

Cause

A VM restore changes the VM MoRef ID in VMware vCenter. This new ID does not synchronize to Aria Automation, causing the Day 2 operation to fail due to a java.lang.IllegalArgumentException: property 'config.name' not fetched exception during resource enumeration.

Resolution

This behaviour is being reviewed and a fix will be made available in the future release.
To address this issue, please log a support request with Broadcom Support by following the steps outlined in this KB

Additional Information

Note: For defects and enhancements, we recommend you subscribe to this article to receive updates on fix status.