Spurious timeout on Cirrus CI

[awelzel]

The following cluster testing run caused a 1h timeout on Cirrus. A retry fixed it.

https://cirrus-ci.com/task/4816352922304512

There might have been something off with the local DNS setup (failure in name resolution errors). Possibly just a one-off with Cirrus CI infrastructure, but creating this issue in case it happens again.

Copy of test output:

[12:42:52.781] cd testing/external/zeek-testing-cluster && ../../../auxil/btest/btest -d -b -j ${ZEEK_CI_BTEST_JOBS}
[12:47:54.644] [#1] tests.stage-config-auto-assign-disabled ... failed
[12:47:54.644]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-auto-assign-disabled/stage-config-auto-assign-disabled.sh' failed unexpectedly (exit code 1)
[12:47:54.644]   % cat .stderr
[12:47:54.644]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:47:54.644]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:47:54.644] 
[12:47:54.845] [#4] tests.stage-config-auto-assign-multi-instance ... failed
[12:47:54.845]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-auto-assign-multi-instance/stage-config-auto-assign-multi-instance.sh' failed unexpectedly (exit code 1)
[12:47:54.845]   % cat .stderr
[12:47:54.845]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:47:54.845]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:47:54.845] 
[12:49:05.480] [#2] tests.restart ... failed
[12:49:05.480]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.restart/restart.sh' failed unexpectedly (exit code 1)
[12:49:05.480]   % cat .diag
[12:49:05.480]   == File ===============================
[12:49:05.480]   {
[12:49:05.480]     "errors": [
[12:49:05.480]       {
[12:49:05.480]         "error": "no instances connected",
[12:49:05.480]         "source": null
[12:49:05.480]       }
[12:49:05.480]     ],
[12:49:05.480]     "results": {}
[12:49:05.480]   }
[12:49:05.480]   == Diff ===============================
[12:49:05.481]   =======================================
[12:49:05.481] 
[12:49:05.481]   % cat .stderr
[12:49:05.481]   Creating network "tests_restart__default" with the default driver
[12:49:05.481]   Creating tests_restart__controller_1 ...
[12:49:05.481]   Creating tests_restart__client_1     ...
[12:49:05.481]   Creating tests_restart__client_1     ... done
[12:49:05.481]   Creating tests_restart__controller_1 ... done
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481]   error: websocket error in connect() with controller controller:2149: [Errno -3] Temporary failure in name resolution
[12:49:05.481] 
[12:50:55.761] [#1] tests.stage-config-auto-assign-new-range ... failed
[12:50:55.761]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-auto-assign-new-range/stage-config-auto-assign-new-range.sh' failed unexpectedly (exit code 1)
[12:50:55.761]   % cat .stderr
[12:50:55.761]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:50:55.761]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:50:55.761] 
[12:50:55.962] [#4] tests.stage-config-conflict-node-agent-ports ... failed
[12:50:55.962]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-conflict-node-agent-ports/stage-config-conflict-node-agent-ports.sh' failed unexpectedly (exit code 1)
[12:50:55.962]   % cat .stderr
[12:50:55.962]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:50:55.962]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:50:55.962] 
[12:52:06.614] [#2] tests.stage-config-conflict-node-controller-port ... failed
[12:52:06.614]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-conflict-node-controller-port/stage-config-conflict-node-controller-port.sh' failed unexpectedly (exit code 1)
[12:52:06.614]   % cat .stderr
[12:52:06.614]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:52:06.614]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:52:06.614] 
[12:53:56.907] [#1] tests.stage-config-conflict-node-ports ... failed
[12:53:56.907]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-conflict-node-ports/stage-config-conflict-node-ports.sh' failed unexpectedly (exit code 1)
[12:53:56.907]   % cat .stderr
[12:53:56.907]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:53:56.907]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:53:56.907] 
[12:53:57.108] [#4] tests.stage-config-deploy ... failed
[12:53:57.108]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-deploy/stage-config-deploy.sh' failed unexpectedly (exit code 1)
[12:53:57.108]   % cat .stderr
[12:53:57.108]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:53:57.108]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:53:57.108] 
[12:55:07.734] [#2] tests.stage-config-empty ... failed
[12:55:07.734]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-empty/stage-config-empty.sh' failed unexpectedly (exit code 1)
[12:55:07.734]   % cat .stderr
[12:55:07.734]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:55:07.734]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:55:07.734] 
[12:56:58.000] [#1] tests.stage-config-invalid-naming ... failed
[12:56:58.000]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-invalid-naming/stage-config-invalid-naming.sh' failed unexpectedly (exit code 1)
[12:56:58.000]   % cat .stderr
[12:56:58.000]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:56:58.000]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:56:58.000] 
[12:56:58.201] [#4] tests.stage-config-mismatch-instance-names ... failed
[12:56:58.201]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-mismatch-instance-names/stage-config-mismatch-instance-names.sh' failed unexpectedly (exit code 1)
[12:56:58.201]   % cat .stderr
[12:56:58.201]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:56:58.201]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:56:58.201] 
[12:58:08.930] [#2] tests.stage-config-then-deploy ... failed
[12:58:08.930]   % 'bash /zeek/testing/external/zeek-testing-cluster/.tmp/tests.stage-config-then-deploy/stage-config-then-deploy.sh' failed unexpectedly (exit code 1)
[12:58:08.930]   % cat .stderr
[12:58:08.930]   An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
[12:58:08.930]   If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
[12:58:08.930] 
[13:42:08.032] 
[13:42:08.032] Timed out!