Delay in VCF Automation 9.x Deployment Power Status Updates

Products

• VCF Automation

Issue/Introduction

When executing Day-2 Power On or Power Off actions on virtual machines in VCF Automation, the deployment status remains unchanged in the user interface for approximately 10–15 minutes, despite the task completing successfully in vCenter. This discrepancy occurs when customized workflows bypass the out-of-the-box (OOTB) VCF Automation power management logic, causing dependent workflows to fail due to outdated status data.

Symptoms:

• Deployment status in VCF Automation portal is delayed after Power On/Off actions.
• VM powers on/off immediately in vCenter and Provisioning DB, but VCFA UI shows old status.
• Dependent workflows fail due to status mismatch.
  

Environment

VCF Automation 9.0.2

Cause

The issue is caused by using the com.vmware.library.vc.vm.power workflow action in customized Day-2 resource actions.

This action updates the power state at the vCenter level but does not trigger the internal VCF Automation resource state update mechanism. Consequently, the UI relies on slower background data collection cycles to synchronize the status.

Resolution

Update all customized workflows to use the VCF Automation-specific power management actions, which ensure the resource state is updated in the VCF Automation database immediately.

• Identify the customized workflow currently calling com.vmware.library.vc.vm.power.
• Modify the workflow to convert the input type from VC:VirtualMachine to VRA:Machine.
• Replace the existing power actions with the following actions from the com.vmware.library.vra.infrastructure.machine.power package:
  powerOnMachine
powerOffMachine
• Save and publish the updated workflow.

Additional Information

For further assistance, Contact Broadcom Support