test: verify nginx returns 502 when coredns-docker is unavailable

Adds bats coverage on the bare-metal CI host (stops `coredns-docker` via `systemctl` and asserts the rendered vhost returns 502, then restarts and asserts recovery to 200) and a parallel `tests/test_coredns_outage` driver wired into `make test-ci-docker` that exercises the same flow against the dokku container using `sv stop|start coredns-docker`. Answers the open thread on whether the resolver-mode upstream surfaces a useful error when the DNS service is down.
This commit is contained in:
Jose Diaz-Gonzalez committed 2026-11-06 20:43:34 -05:00
1 parent 599bc7b243
commit ea72a80139
3 files changed
+136 -1

No files matched your search

+25
View File
@@ -9,6 +9,7 @@ setup() {
}
teardown() {
sudo systemctl start coredns-docker >/dev/null 2>&1 || true
dokku --quiet nginx:set --global dns-resolver
dokku --quiet nginx:set --global dns-zone
destroy_app
@@ -137,3 +138,27 @@ teardown() {
assert_output_not_contains "\$dokku_upstream"
assert_output_contains "upstream ${TEST_APP}-"
}
@test "(nginx-vhosts) nginx returns 502 when coredns-docker is stopped" {
run deploy_app python dokku@$DOKKU_DOMAIN:$TEST_APP
echo "output: $output"
echo "status: $status"
assert_success
run sudo systemctl stop coredns-docker
echo "output: $output"
echo "status: $status"
assert_success
run curl --connect-to "$TEST_APP.$DOKKU_DOMAIN:80:localhost:80" -kSso /dev/null -w "%{http_code}" -m 5 "http://$TEST_APP.$DOKKU_DOMAIN/"
echo "output: $output"
echo "status: $status"
assert_output "502"
run sudo systemctl start coredns-docker
echo "output: $output"
echo "status: $status"
assert_success
assert_http_localhost_response http "$TEST_APP.$DOKKU_DOMAIN" 80 / "" 200
}