kubeadm: kubeadm init --kubernetes-version ci-cross/latest fails to pull the images

Is this a BUG REPORT or FEATURE REQUEST?

Choose one: BUG REPORT

Versions

kubeadm version (use kubeadm version):

root@ip:~ # kubeadm version kubeadm version: &version.Info{Major:“1”, Minor:“12+”, GitVersion:“v1.12.0-alpha.0.2473+fea4ad2783f59d”, GitCommit:“fea4ad2783f59d44cc0db907523a07499db172ec”, GitTreeState:“clean”, BuildDate:“2018-07-27T03:13:19Z”, GoVersion:“go1.10.3”, Compiler:“gc”, Platform:“linux/ppc64le”} root@ip:~ #

Environment:

• Kubernetes version (use kubectl version): root@ip:~ # kubectl version Client Version: version.Info{Major:“1”, Minor:“12+”, GitVersion:“v1.12.0-alpha.0.2473+fea4ad2783f59d”, GitCommit:“fea4ad2783f59d44cc0db907523a07499db172ec”, GitTreeState:“clean”, BuildDate:“2018-07-27T03:16:27Z”, GoVersion:“go1.10.3”, Compiler:“gc”, Platform:“linux/ppc64le”} The connection to the server ip:8001 was refused - did you specify the right host or port? root@ip:~ #
• Cloud provider or hardware configuration: ppc64le
• OS (e.g. from /etc/os-release): root@ip:~ # cat /etc/os-release NAME=“Ubuntu” VERSION=“16.04.4 LTS (Xenial Xerus)” ID=ubuntu ID_LIKE=debian PRETTY_NAME=“Ubuntu 16.04.4 LTS” VERSION_ID=“16.04” HOME_URL=“http://www.ubuntu.com/” SUPPORT_URL=“http://help.ubuntu.com/” BUG_REPORT_URL=“http://bugs.launchpad.net/ubuntu/” VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial root@ip:~ #
• Kernel (e.g. uname -a): root@ip:~ # uname -a Linux ip 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ip:~ #
• Others:

What happened?

root@ip:~ # kubeadm init --kubernetes-version ci-cross/latest [init] using Kubernetes version: v1.12.0-alpha.0.2473+fea4ad2783f59d [preflight] running pre-flight checks I0726 23:51:46.864964 11860 kernel_validator.go:81] Validating kernel version I0726 23:51:46.865467 11860 kernel_validator.go:96] Validating kernel config [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.03.1-ce. Max validated version: 17.03 [WARNING Service-Kubelet]: kubelet service is not enabled, please run ‘systemctl enable kubelet.service’ [preflight/images] Pulling images required for setting up a Kubernetes cluster [preflight/images] This might take a minute or two, depending on the speed of your internet connection [preflight/images] You can also perform this action in beforehand using ‘kubeadm config images pull’ [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to check if image gcr.io/kubernetes-ci-images/kube-apiserver-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d exists: output: [] Error: No such object: gcr.io/kubernetes-ci-images/kube-apiserver-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d , error: exit status 1 [ERROR ImagePull]: failed to check if image gcr.io/kubernetes-ci-images/kube-controller-manager-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d exists: output: [] Error: No such object: gcr.io/kubernetes-ci-images/kube-controller-manager-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d , error: exit status 1 [ERROR ImagePull]: failed to check if image gcr.io/kubernetes-ci-images/kube-scheduler-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d exists: output: [] Error: No such object: gcr.io/kubernetes-ci-images/kube-scheduler-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d , error: exit status 1 [ERROR ImagePull]: failed to check if image gcr.io/kubernetes-ci-images/kube-proxy-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d exists: output: [] Error: No such object: gcr.io/kubernetes-ci-images/kube-proxy-ppc64le:v1.12.0-alpha.0.2473_fea4ad2783f59d , error: exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=... root@ip:~ #

What you expected to happen?

cluster should have come up

How to reproduce it (as minimally and precisely as possible)?

run kubeadm init --kubernetes-version ci-cross/latest with latest version of kubeadm on ppc64le