2019-07-24 01:08:36 +00:00
|
|
|
#!/usr/bin/env bats
|
|
|
|
|
|
|
|
load helpers
|
|
|
|
|
|
|
|
@test "s1 proxy admin is up on :19000" {
|
|
|
|
retry_default curl -f -s localhost:19000/stats -o /dev/null
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s2 proxy admin is up on :19001" {
|
|
|
|
retry_default curl -f -s localhost:19001/stats -o /dev/null
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3-v1 proxy admin is up on :19002" {
|
|
|
|
retry_default curl -f -s localhost:19002/stats -o /dev/null
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3-v2 proxy admin is up on :19003" {
|
|
|
|
retry_default curl -f -s localhost:19003/stats -o /dev/null
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3 proxy admin is up on :19004" {
|
|
|
|
retry_default curl -f -s localhost:19004/stats -o /dev/null
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s1 proxy listener should be up and have right cert" {
|
|
|
|
assert_proxy_presents_cert_uri localhost:21000 s1
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s2 proxy listener should be up and have right cert" {
|
|
|
|
assert_proxy_presents_cert_uri localhost:21001 s2
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3-v1 proxy listener should be up and have right cert" {
|
|
|
|
assert_proxy_presents_cert_uri localhost:21002 s3
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3-v2 proxy listener should be up and have right cert" {
|
|
|
|
assert_proxy_presents_cert_uri localhost:21003 s3
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3 proxy listener should be up and have right cert" {
|
|
|
|
assert_proxy_presents_cert_uri localhost:21004 s3
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s2 proxies should be healthy" {
|
|
|
|
assert_service_has_healthy_instances s2 1
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s3 proxies should be healthy" {
|
|
|
|
assert_service_has_healthy_instances s3 3
|
|
|
|
}
|
|
|
|
|
|
|
|
# Note: when failover is configured the cluster is named for the original
|
|
|
|
# service not any destination related to failover.
|
|
|
|
@test "s1 upstream should have healthy endpoints for s2 and s3 together" {
|
2023-02-23 16:32:32 +00:00
|
|
|
assert_upstream_has_endpoints_in_status 127.0.0.1:19000 failover-target~1~s2.default.primary HEALTHY 1
|
2019-07-24 01:08:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
@test "s1 upstream should be able to connect to s2 via upstream s2 to start" {
|
|
|
|
assert_expected_fortio_name s2
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "terminate instance of s2 envoy which should trigger failover to s3 when tcp check fails" {
|
|
|
|
kill_envoy s2
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "s1 upstream should have healthy endpoints for s3-v1 and unhealthy endpoints for s2" {
|
2023-02-23 16:32:32 +00:00
|
|
|
assert_upstream_has_endpoints_in_status 127.0.0.1:19000 failover-target~1~s2.default.primary HEALTHY 1
|
|
|
|
assert_upstream_has_endpoints_in_status 127.0.0.1:19000 failover-target~0~s2.default.primary UNHEALTHY 1
|
2019-07-24 01:08:36 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
@test "s1 upstream should be able to connect to s3-v1 now" {
|
|
|
|
assert_expected_fortio_name s3-v1
|
|
|
|
}
|