View can repeatedly delete and recreate linked-clone and full-clone machines that are in an Error state.
Problem
A linked-clone or full-clone machine is created in an Error state, deleted, and recreated in an Error state. This cycle keeps repeating.
Cause
When a large desktop pool is provisioned, one or more virtual machines might end up in an Error state. The View automatic recovery mechanism attempts to power on the failed virtual machine. If the virtual machine does not power on after a certain number of attempts, View deletes the virtual machine.
Following the pool size requirements, View creates a new virtual machine, often with the same machine name as the original machine. If the new virtual machine is provisioned with the same error, that virtual machine is deleted, and the cycle repeats.
Automatic recovery is performed on linked-clone and full-clone machines.
If automatic recovery attempts fail for a virtual machine, View deletes the virtual machine only if it is a floating machine or a dedicated machine that is not assigned to a user. Also, View does not delete virtual machines when pool provisioning is disabled.
Solution
Examine the parent virtual machine or template that was used to create the desktop pool. Check for errors in the virtual machine or guest operating system that might cause the error in the virtual machine.
For linked clones, resolve errors in the parent virtual machine and take a new snapshot.
- If many machines are in an Error state, use the new snapshot or template to recreate the pool.
- If most machines are healthy, select the desktop pool in View Administrator, click Edit, select the vCenter Settings tab, select the new snapshot as a default base image, and save your edits.
New linked-clone machines are created using the new snapshot.
For full clones, resolve errors in the virtual machine, generate a new template, and recreate the pool.
