vSphere Auto Deploy Rule Takes Long to Complete

After you run an Auto Deploy rule, it takes long to complete, and you see no progress for the tasks.

Problem

Auto Deploy automatically detects if a new version of the image that a cluster uses is available, or when the cache lifetime of files expires, and refreshes the cache by re-downloading the files from the latest version of the software depot. As a result, you might see a delay in the implementation of Auto Deploy rules.

Cause

When the cache lifetime of files cached by Auto Deploy expires, Auto Deploy automatically refreshes the cache from the software depot. Since a default software depot is usually more than 300 MB, depending on the network, the download might take long.

You can also see a delay in deploying Auto Deploy rules when converting a cluster that you manage with a single image to one that you manage with a configuration on a cluster level. If a host attempts to boot during the time Auto Deploy caches the configuration file, you might see a delay, because of the time Auto Deploy needs to create the cache.

A general vSphere infrastructure problem might also prevent Auto Deploy rules from running in a timely manner.

Solution

• ♦ Regardless of any connectivity issues or breakage, Auto Deploy keeps active sessions and persists in booting hosts until it succeeds.