We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
I noticed that than I was following tutorial command failed
dig -p 5053 +tcp @localhost localtargets-roundrobin.cloud.example.com && \ dig -p 5054 +tcp @localhost localtargets-roundrobin.cloud.example.com
After running make terratest command received that error
make terratest
=== RUN TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: Running command dig with args [-p5053 @localhost terratest-failover-split.cloud.example.com +short +tcp] TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ;; communications error to 127.0.0.1#5053: connection reset TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ;; communications error to 127.0.0.1#5053: end of file TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ;; communications error to 127.0.0.1#5053: connection reset TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> -p5053 @localhost terratest-failover-split.cloud.example.com +short +tcp TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ; (1 server found) TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ;; global options: +cmd TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: ;; no servers could be reached TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again 2023-10-24T16:43:22+02:00 logger.go:66: command.go:50: Error Trace: /home/augustris/k8gb/terratest/test/command.go:50 /home/augustris/k8gb/terratest/test/utils.go:70 /home/augustris/k8gb/terratest/test/utils.go:235 /home/augustris/k8gb/terratest/test/utils.go:85 /home/augustris/k8gb/terratest/test/utils.go:230 /home/augustris/k8gb/terratest/test/k8gb_split_failover_test.go:118 Error: Received unexpected error: error while running command: exit status 9; Test: TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again TestK8gbSplitFailoverExample 2023-10-24T16:43:22+02:00 client.go:42: Configuring Kubernetes client using config file /home/augustris/.kube/config with context k3d-test-gslb2 TestK8gbSplitFailoverExample 2023-10-24T16:43:22+02:00 client.go:42: Configuring Kubernetes client using config file /home/augustris/.kube/config with context k3d-test-gslb1 --- FAIL: TestK8gbSplitFailoverExample (137.40s) --- FAIL: TestK8gbSplitFailoverExample/Each_cluster_resolves_its_own_set_of_IP_addresses (0.04s) --- PASS: TestK8gbSplitFailoverExample/serviceHealth_becomes_Unhealthy_after_scaling_down_to_0 (0.29s) --- FAIL: TestK8gbSplitFailoverExample/Cluster_1_failovers_to_Cluster_2 (0.03s) --- FAIL: TestK8gbSplitFailoverExample/Cluster_2_still_returns_own_entries (0.04s) --- PASS: TestK8gbSplitFailoverExample/serviceHealth_becomes_Healthy_after_scaling_up (3.73s) --- FAIL: TestK8gbSplitFailoverExample/Cluster_1_returns_own_entries_again (0.04s) FAIL exit status 1 FAIL k8gbterratest/test 137.483s make: *** [Makefile:452: terratest] Error 1
k3d version v5-dev k3s version v1.21.7-k3s1 (default)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I noticed that than I was following tutorial command failed
After running
make terratest
command received that errork3d version v5-dev
k3s version v1.21.7-k3s1 (default)
The text was updated successfully, but these errors were encountered: