VCF Automation Node Fails to Redeploy Automatically After Single node lost

Products

• VCF Automation

Issue/Introduction

In a VMware Cloud Foundation (VCF) environment, a VCF Automation cluster node is removed due to a 'datastore full' exception. 

Despite documentation stating that a single node failure should be automatically remediated, the failed node does not automatically redeploy, leaving the cluster with only two active nodes.

Environment

VCF Automation 9.0.2

Cause

The automatic redeployment mechanism relies on the presence of the vcf-services-runtime-template in vCenter.

If this template is manually removed or missing from its expected path, VCF Automation cannot initiate the automatic recovery and redeployment of the missing node.

Resolution

To resolve this issue and trigger the automatic reconstruction of the third node, ensure the runtime template is restored to its original location:

• Check if vcf-services-runtime-template exists in the vCenter inventory.
• If missing, restore or recreate the vcf-services-runtime-template in its original inventory path.
• Once the template is restored, VCF Automation will detect the inconsistency and automatically start the reconstruction of the missing third node.

Additional Information

** Important ** Do not manually delete the vcf-services-runtime-template. This template is critical for the health and self-healing capabilities (Fleet Management) of the VCF Automation services.

Restore VCF Automation

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/fleet-management/backup-and-restore-of-cloud-foundation/restore-vcf-automation.html