VCF Stretch cluster workflow fails on subtask apply storage policy

Products

• VMware Cloud Foundation

Issue/Introduction

Stretch cluster workflow fails during operation in apply storage policy action. 

VCF stretch cluster operation task fails with sub-task:

Failed
Message: Failed to update and re-apply vSAN storage policy VsanDefaultProfile.

Remediation Message:
Reference Token: XXXXXX
Cause: Exception [Task: (MOR:task-XXXX) (Name:reconfigure) Entity: (MOR:vm-XX) (Name:vcf-services-platform-template-9.0.X.X.XXXXXXXX) is failed] while waiting for reconfiguring task to end task id : task-XXXX Task: (MOR:task-XXXX) (Name:reconfigure) Entity: (MOR:vm-XX) (Name:vcf-services-platform-template-9.0.X.X.XXXXXXXX) is failed The operation is not supported on the object.

SDDC Manager logs may show (/var/log/vmware/vcf/domainmanager/domainmanager.log)

VSAN_DEFAULT_STORAGE_POLICY_UPDATION_FAILED Failed to update and re-apply vSAN storage policy VsanDefaultProfile.

vCenter logs may show (/var/log/vmware/vxpd/vpxd.log)

error vpxd[23921] [Originator@6876 sub=vmmoVm opID=ea435123-d39d-4987-b22c-b65fdf282231-997638-314-a7] Template reconfigure only allows name and annotation change.

 

Environment

VCF 9.0.X

vSAN 9.0.X

VCF Automation 9.0.X

 

 

 

 

Cause

If any VM templates are registered in the target cluster, the stretch cluster operation will fail while applying the storage policy action.

Resolution

Workaround:

Before stretching an existing VCF Cluster:

Before starting the stretch cluster operation, make sure that any VM templates are converted to VMs.
To alter an existing template, you must convert it to a virtual machine, make the required changes, and convert the virtual machine back to a template.
For details on the procedure please review  https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/9-0/convert-a-template-to-a-virtual-machine.html

Once the stretch operation is finished, return the VMs to the VM template format.

Failed stretch cluster operation:

The above workaround will also work in the event of a failed workflow, simply apply the above workaround and retry the task on VCF.