Open ijc opened 6 years ago
For the kube-dns
issue the distribution of iterations for success is potentially interesting:
[go:LinuxKit] ijc@bokrug:test$ sed -n -E -e 's/.*(SUCCESS await kube-dns ready..after)/\1/g'p results-cc58ae93ccbfe8f4acdbb209394fe8af3d06bede.0/*/k*cri-bridge*.log | sort -k6 -n | uniq -c
2 SUCCESS await kube-dns ready (after 19 attempts)
9 SUCCESS await kube-dns ready (after 20 attempts)
37 SUCCESS await kube-dns ready (after 21 attempts)
35 SUCCESS await kube-dns ready (after 22 attempts)
13 SUCCESS await kube-dns ready (after 23 attempts)
1 SUCCESS await kube-dns ready (after 24 attempts)
1 SUCCESS await kube-dns ready (after 50 attempts)
1 SUCCESS await kube-dns ready (after 92 attempts)
[go:LinuxKit] ijc@bokrug:test$ sed -n -E -e 's/.*(SUCCESS await kube-dns ready..after)/\1/g'p results-cc58ae93ccbfe8f4acdbb209394fe8af3d06bede.0/*/k*cri-weave*.log | sort -k6 -n | uniq -c
2 SUCCESS await kube-dns ready (after 9 attempts)
5 SUCCESS await kube-dns ready (after 10 attempts)
7 SUCCESS await kube-dns ready (after 11 attempts)
9 SUCCESS await kube-dns ready (after 12 attempts)
5 SUCCESS await kube-dns ready (after 13 attempts)
8 SUCCESS await kube-dns ready (after 14 attempts)
3 SUCCESS await kube-dns ready (after 15 attempts)
5 SUCCESS await kube-dns ready (after 16 attempts)
6 SUCCESS await kube-dns ready (after 17 attempts)
5 SUCCESS await kube-dns ready (after 18 attempts)
8 SUCCESS await kube-dns ready (after 19 attempts)
5 SUCCESS await kube-dns ready (after 20 attempts)
9 SUCCESS await kube-dns ready (after 21 attempts)
7 SUCCESS await kube-dns ready (after 22 attempts)
9 SUCCESS await kube-dns ready (after 23 attempts)
4 SUCCESS await kube-dns ready (after 24 attempts)
1 SUCCESS await kube-dns ready (after 36 attempts)
[go:LinuxKit] ijc@bokrug:test$ sed -n -E -e 's/.*(SUCCESS await kube-dns ready..after)/\1/g'p results-cc58ae93ccbfe8f4acdbb209394fe8af3d06bede.0/*/k*docker-bridge*.log | sort -k6 -n | uniq -c
3 SUCCESS await kube-dns ready (after 6 attempts)
48 SUCCESS await kube-dns ready (after 7 attempts)
38 SUCCESS await kube-dns ready (after 8 attempts)
10 SUCCESS await kube-dns ready (after 9 attempts)
1 SUCCESS await kube-dns ready (after 10 attempts)
[go:LinuxKit] ijc@bokrug:test$ sed -n -E -e 's/.*(SUCCESS await kube-dns ready..after)/\1/g'p results-cc58ae93ccbfe8f4acdbb209394fe8af3d06bede.0/*/k*docker-weave*.log | sort -k6 -n | uniq -c
1 SUCCESS await kube-dns ready (after 2 attempts)
2 SUCCESS await kube-dns ready (after 5 attempts)
1 SUCCESS await kube-dns ready (after 6 attempts)
4 SUCCESS await kube-dns ready (after 7 attempts)
1 SUCCESS await kube-dns ready (after 8 attempts)
3 SUCCESS await kube-dns ready (after 11 attempts)
7 SUCCESS await kube-dns ready (after 12 attempts)
14 SUCCESS await kube-dns ready (after 13 attempts)
12 SUCCESS await kube-dns ready (after 14 attempts)
18 SUCCESS await kube-dns ready (after 15 attempts)
18 SUCCESS await kube-dns ready (after 16 attempts)
15 SUCCESS await kube-dns ready (after 17 attempts)
3 SUCCESS await kube-dns ready (after 18 attempts)
1 SUCCESS await kube-dns ready (after 20 attempts)
I ran 100 iterations of
rtf test
on commit cc58ae93ccbfe8f4acdbb209394fe8af3d06bede. Results were:The
await kube-dns ready
failures (which appearcri
specific, although that might just be a timing thing) all follow the pattern:That is around a dozen iterations over 40-80s and then silence until the overall timeout after 300s. I suspect this is a test case issue.
The
intra-pod networking
failure which appears docker-bridge specific is the same in every case too, that is it is actually failing to install curl:This isn't caught so it then does lots of
before timing out.
results-cc58ae93ccbfe8f4acdbb209394fe8af3d06bede.zip