Change:
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT Kubernetes version (use ): community master Environment: Cloud provider or hardware configuration: my local machine OS (e.g. from /etc/os-release): linux Kernel (e.g. ): Linux localhost.localdomain 4.10.8-200.fc25.x8664 SMP Fri Mar 31 13:20:22 UTC 2017 x8664 x8664 x8664 GNU/Linux Install tools: Others: ipv6 is disabled in my environment. What happened: ' Running tests for APIVersion: v1,,,apps/v1beta1,,,,,autoscaling/v1,autoscaling/v2alpha1,batch/v1,batch/v2alpha1,,extensions/v1beta1,,,policy/v1beta1,,,,,,federation/v1beta1 +++ [0611 16:37:17] Running tests without code coverage === RUN TestCertsTLS --- FAIL: TestCertsTLS (5.11s) [0] unexpected error: dial tcp [::]:: connect: cannot assign requested address [1] unexpected error: dial tcp [::]:: connect: cannot assign requested address [2] unexpected error: dial tcp [::]:: connect: cannot assign requested address [3] unexpected error: dial tcp [::]:: connect: cannot assign requested address [4] unexpected error: dial tcp [::]:: connect: cannot assign requested address [5] unexpected error: dial tcp [::]:: connect: cannot assign requested address [6] unexpected error: want x509.HostnameError, got: net.OpError [7] unexpected error: want x509.HostnameError, got: net.OpError [8] unexpected error: want x509.HostnameError, got: net.OpError [9] unexpected error: want x509.HostnameError, got: net.OpError [10] unexpected error: want x509.UnknownAuthorityError, got: net.OpError [11] unexpected error: want x509.UnknownAuthorityError, got: net.OpError [12] unexpected error: want x509.HostnameError, got: net.OpError [13] unexpected error: want x509.HostnameError, got: net.OpError FAIL exit status 1 FAIL 5.391s Makefile:164: recipe for target 'test' failed make: [test] Error 1 What you expected to happen: Unit test should passes. How to reproduce it (as minimally and precisely as possible): This always happens in my environment. Anything else we need to know*:
There are no sig labels on this issue. Please by:<br(1) mentioning a sig: <br(2) specifying the label manually: <br<brNote: method (1) will trigger a notification to the team. You can find the team list and label list
What version of go are you using?
I use go version go1.8.1 linux/amd64.
/sig auth
When I enable IPV6, this test passes. this to /etc/sysctl.d/99- sysctl -w
The same failures are occurring with my PR's unit tests https://k8s-
I'm seeing this failure on a PR too https://k8s-
This is probably what we are seeing:
And fixed in golang, probably for 1.9: https://go-
I'm seeing these same errors in PRs against the 1.7 () and 1.5 branches () . Does this fix need to be backported ?
Oh wait, I can see it in 1.7, I'll rebase now :)

Discussion:
} }() <del> c, err := tls.Dial("tcp", s.Addr().String(), cCfg) </del> <ins> // workaround [::] not working in ipv4 only systems (https://github.com/golang/go/issues/18806) // TODO: remove with Golang 1.9 with https://go-review.googlesource.com/c/45088/ addr := strings.TrimPrefix(s.Addr().String(), "[::]") c, err := tls.Dial("tcp", addr, cCfg) </ins> if err != nil { // Intentionally not serializing the error received because we want to // test for the failure case in the caller test function.