Symptoms:
Resource [/resources/compute/<UUID_1>]:: Salt resource with job id [<UUID_1>] failed. Error:: Timeout: Salt server did not respond in 30 minutes for job id [<UUID_1>]
This issue is resolved in VMware Aria Automation Config 8.12.1.
To workaround the timeout:
createTimeout
the can either have values that end in m (for minutes) or h (for hours). See the example below:
Cloud_SaltStack:
type: Cloud.SaltStack
...
# Field to extend timeout
createTimeout: 1h
...
/etc/raas/raas.conf
the additional parameters can be added as well. These changes will take effect once the raas service has been restarted (systemctl restart raas)
sseapi_win_minion_deploy_delay: 360 # Sets a delay to allow all requisite Windows services to become active. The default value is 180 seconds
sseapi_linux_minion_deploy_delay: 120 # Sets a delay to allow all requisite Linux services to become activate. The default value is 90 seconds.
# Minion deployment settings
minion_deployment:
max_minion_deployment_time: 3600 # Maximum time (in seconds) allowed for minion deployment after which status will be marked as failed
airgap_install: false # Deploy minions in an airgapped environment
.