This seems to be related to the recent bug for kube-kubectl ( bug 693548 ) and unsupported version of go ( =dev-lang/go-1.13 ). Reproducible: Always [32;01m * [39;49;00mPackage: sys-cluster/kube-scheduler-1.16.2 [32;01m * [39;49;00mRepository: gentoo [32;01m * [39;49;00mMaintainer: mrueg@gentoo.org [32;01m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU [32;01m * [39;49;00mFEATURES: network-sandbox preserve-libs sandbox selinux sesandbox userpriv usersandbox >>> Unpacking source... >>> Source unpacked in /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work >>> Preparing source in /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2 ... make -j17 -j1 -C src/k8s.io/kubernetes WHAT=cmd/kube-scheduler GOFLAGS=-v make: Entering directory '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes' make[1]: Entering directory '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes' go: bitbucket.org/bertimus9/systemstat@v0.0.0-20180207000608-0eeff89b0690: Get https://proxy.golang.org/bitbucket.org/bertimus9/systemstat/@v/v0.0.0-20180207000608-0eeff89b0690.mod: dial tcp: lookup proxy.golang.org: no such host +++ [1031 01:12:12] Building go targets for linux/amd64: ./vendor/k8s.io/code-generator/cmd/deepcopy-gen go: bitbucket.org/bertimus9/systemstat@v0.0.0-20180207000608-0eeff89b0690: Get https://proxy.golang.org/bitbucket.org/bertimus9/systemstat/@v/v0.0.0-20180207000608-0eeff89b0690.mod: dial tcp: lookup proxy.golang.org: no such host !!! [1031 01:12:12] Call tree: !!! [1031 01:12:12] 1: /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes/hack/lib/golang.sh:714 kube::golang::build_some_binaries(...) !!! [1031 01:12:12] 2: /var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes/hack/lib/golang.sh:853 kube::golang::build_binaries_for_platform(...) !!! [1031 01:12:12] 3: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) !!! [1031 01:12:12] Call tree: !!! [1031 01:12:12] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) !!! [1031 01:12:12] Call tree: !!! [1031 01:12:12] 1: hack/make-rules/build.sh:27 kube::golang::build_binaries(...) make[1]: *** [Makefile.generated_files:200: _output/bin/deepcopy-gen] Error 1 make[1]: Leaving directory '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes' make: *** [Makefile:559: generated_files] Error 2 make: Leaving directory '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2/src/k8s.io/kubernetes' [31;01m*[0m ERROR: sys-cluster/kube-scheduler-1.16.2::gentoo failed (compile phase): [31;01m*[0m emake failed [31;01m*[0m [31;01m*[0m If you need support, post the output of `emerge --info '=sys-cluster/kube-scheduler-1.16.2::gentoo'`, [31;01m*[0m the complete build log and the output of `emerge -pqv '=sys-cluster/kube-scheduler-1.16.2::gentoo'`. [31;01m*[0m The complete build log is located at '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/temp/environment'. [31;01m*[0m Working directory: '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2' [31;01m*[0m S: '/var/tmp/portage/sys-cluster/kube-scheduler-1.16.2/work/kube-scheduler-1.16.2'
Created attachment 594622 [details] build.log
Other related kubernetes packages are affected as well. * =sys-cluster/kube-scheduler-1.16.2 * =sys-cluster/kube-apiserver-1.16.2 * =sys-cluster/kube-controller-manager-1.16.2 * =sys-cluster/kubelet-1.16.2 * =sys-cluster/kube-proxy-1.16.2 Similarly, as I have observed, as well as is indicated in that previously-referenced bug, this issue may also be true for the 1.15.4 versions of the packages. As of right now, only sys-cluster/kubectl has been addressed and resolved.
There's an upstream tracker for adopting golang-1.13. https://github.com/kubernetes/kubernetes/issues/82531 For the time being, the workaround is to remove go.mod from the sources.
