Symptoms
Instant clone push operation fails with an error :
Fault type is UNKNOWN_FAULT_FATAL - After waiting for 300 seconds internal template VM.
Upon reviewing the Debug logs from Connection Server - The Image waits for 300 seconds and then fails with an exception:-
2023-09-30T09:17:57.495-05:00 WARN (0ED8-18E8) <WFE-14> [Action] The VC Operation failed with error: com.vmware.daas.cloneprep.common.CPException: After waiting for 300 seconds internal template VM: vm-xxxxx is still not powered off. Giving up!
2023-09-30T09:17:57.496-05:00 ERROR (0ED8-0E9C) <WFE-19> [Task] WaitForInternalTemplateAction of Task=[PrepareInternalTemplateTask:c10f26b8-1def-4db1-9814-d4664cfcdc1c:1672355], requestId=ee86de5d-491d-463e-87f9-06ea77a3a365 failed at index=5 with com.vmware.daas.cloneprep.common.CPException: After waiting for 300 seconds internal template VM: vm-xxxxx is still not powered off. Giving up!
Purpose
Instant clone push operation fails with an error Fault type is UNKNOWN_FAULT_FATAL - After waiting for 300 seconds internal template VM.
Cause
The internal template has a default of 5 minutes (300 seconds) to complete customization before it will time out.Note: The internal template 300 seconds cannot be configured or modified as it's hard coded.Example:Domain join usually takes more than a minute. So for instance , if a gpupdate takes more than 4 minutes, it's going to timeout.
Impact / Risks
Unable to create Instant Clone VMs.
Resolution
This issue may occur if Group Policy updates takes too long on the CP-Template and this requires internal assessment within your organization to improve the performance / duration of the updates.
Workaround
To isolate the issue if the group policy update is contributing to the time out , you can set the following registry on the parent image
HKLM\Software\VMware, Inc.\ViewComposer\ga\GPUpdateEnabledOnIT
DWORD 0
If this works then to address the issue GPO related issues needs to be fixed.This key is to assist with isolating the issue and it is not recommended as a solution.
You can block inheritance and iteratively test policies to isolate the problematic policy.You can follow industry best practices in terms of troubleshooting GP performance.
