You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2023. It is now read-only.
with image based installs (branch feat118), when the following happens
INFO: Deleting VM ID sattestclient02.sattest.pcfe.net [Fri May 1 03:04:29 CEST 2020]
Host deleted.
INFO: Recreating VM ID sattestclient02.sattest.pcfe.net [Fri May 1 03:04:35 CEST 2020]
Could not create the host:
Render user data template for sattestclient02.sattest.pcfe.net task failed with the following error: execution expired
then 6000 seconds later
[...]
INFO: Waiting 1 minute [Fri May 1 04:48:16 CEST 2020]
INFO: Checking if host sattestclient02.sattest.pcfe.net is in build mode. [Fri May 1 04:49:16 CEST 2020]
Error: host not found.
host sattestclient02.sattest.pcfe.net is still in build mode. [Fri May 1 04:49:18 CEST 2020]
INFO: Waiting 1 minute [Fri May 1 04:49:18 CEST 2020]
INFO: Checking if host sattestclient02.sattest.pcfe.net is in build mode. [Fri May 1 04:50:18 CEST 2020]
Error: host not found.
host sattestclient02.sattest.pcfe.net is still in build mode. [Fri May 1 04:50:21 CEST 2020]
ERROR: At least one host still in build mode after 6000 seconds. Exiting. [Fri May 1 04:50:21 CEST 2020]
obviously it would be better if such a run would error out when Could not create the host: happens instead of waiting until the timeout (6000 seconds in this example) is reached.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
with image based installs (branch feat118), when the following happens
then 6000 seconds later
obviously it would be better if such a run would error out when
Could not create the host:
happens instead of waiting until the timeout (6000 seconds in this example) is reached.The text was updated successfully, but these errors were encountered: