VM Status Information Missing in VCF Automation 9.0.x Deployments
search cancel

VM Status Information Missing in VCF Automation 9.0.x Deployments

book

Article ID: 435137

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

When deploying a virtual machine (VM) from the catalog in VCF Automation 9.0.1 (formerly VMware Aria Automation), the Status information for the deployment object may appear empty: showing only as {} in the Automation UI.

  • External Orchestrator workflows that rely on VM properties (such as VMIDs or host information) fail because the data is not yet populated.
  • The status information typically becomes visible only after the VM is power cycled

Environment

VCF Automation 9.0.x

Cause

This issue is caused by a race condition between the supervisor resource creation and the internal data collection process. Specifically, the supervisor resource may present non-reconciled or stale properties if the deployment blueprint does not explicitly wait for the VM creation to complete.

Without a defined wait condition, the platform proceeds to mark the resource as created before the underlying vSphere/Supervisor metadata has been synchronized back to the Automation database.

Resolution

To resolve this issue, you must modify the Cloud Template (blueprint) to include a wait condition within the properties of the CCI.Supervisor.Resource. This ensures the resource status is not finalized until the VirtualMachineCreated condition is met.

Steps to Update the Blueprint

  1. Log in to the VCF Automation tenant portal.
  2. Open the affected Cloud Template (Blueprint).
  3. Locate the resource of type CCI.Supervisor.Resource.
  4. Add a wait block under the properties section, at the same indentation level as the manifest section.
CCI_Supervisor_Resource_1:
    type: CCI.Supervisor.Resource
    properties:
      context: ${resource.CCI_Supervisor_Namespace_1.id}
      manifest:
        apiVersion: vmoperator.vmware.com/v1alpha3
        kind: VirtualMachine
        [... rest of your manifest ...]
      wait:
        conditions:
          - type: VirtualMachineCreated
            status: 'True'
  1. Version and Release the updated template to the Catalog.
  2. Deploy a new instance to verify that the Status information is populated immediately upon completion.

Note: A permanent fix for this race condition is planned for the VCF Automation 9.1 release.