Symptoms
After encountering an Internal replica error during the first Push Image attempt, the subsequent Re-Push Image on the same snapshot also fails.
Instant Clone provisioning fails during internal replica creation An error " UNKNOWN_FAULT_FATAL: After waiting for 600 seconds Replica vm-xxxx still has not finished customization. Giving up!" appears in the horizonDebug Mode is initiated. Reference: Troubleshooting Instant Clones in the Internal VM Debug ModeIf the same base image and snapshot is used to push another attempt, a message similar to the one below is observed in Connection Server Logs Location of Horizon View log files (1027744)
2023-04-10T00:00:00.000+09:00 ERROR (14C0-0B1C) <PendingOperation-vm-XXXX:snapshot-YYYY-SchedulePushImage> [NgvcHelper] Priming of pool XXX has failed. - UNKNOWN_FAULT_FATAL: Failed to retrieve snapshot for the vm : cp-replica-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Cause
The cause of this issue is related to the failure of Internal VM customization during the initial Push Image attempt, which prevents the snapshot from being taken. If DEBUG mode is enabled, the problematic Internal VM will not be cleaned up, leading to errors during subsequent image pushes.Note, this message can also potentially appear if a snapshot path or the permission needed for Horizon to access the snapshot is altered or objects are modified.
Resolution
To resolve this issue:
Please turn off Internal VM Debug Mode Reference: Troubleshooting Instant Clones in the Internal VM Debug ModeDelete the Internal VM that caused the error.It may also be necessary to investigate the cause of the first Push Image failure. Please see Horizon View Best Practices: Instant Clone Provisioning and Troubleshooting (91265) for general guidance on this.
Related Information
This is a child article of UNKNOWN_FAULT_FATAL: An Index of Instant Clone Creation Errors caused by an Unknown Fault (91729)
