Terraform apply fails on ARM

[zjor]

scaleway_server.k8s_master: Still creating... (16m50s elapsed)

scaleway_server.k8s_master (remote-exec):       Unfortunately, an error has occurred:
scaleway_server.k8s_master (remote-exec):           timed out waiting for the condition

scaleway_server.k8s_master (remote-exec):       This error is likely caused by:
scaleway_server.k8s_master (remote-exec):           - The kubelet is not running
scaleway_server.k8s_master (remote-exec):           - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
scaleway_server.k8s_master (remote-exec):           - No internet connection is available so the kubelet cannot pull or find the following control plane images:
scaleway_server.k8s_master (remote-exec):               - k8s.gcr.io/kube-apiserver-arm:v1.11.4
scaleway_server.k8s_master (remote-exec):               - k8s.gcr.io/kube-controller-manager-arm:v1.11.4
scaleway_server.k8s_master (remote-exec):               - k8s.gcr.io/kube-scheduler-arm:v1.11.4
scaleway_server.k8s_master (remote-exec):               - k8s.gcr.io/etcd-arm:3.2.18
scaleway_server.k8s_master (remote-exec):               - You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
scaleway_server.k8s_master (remote-exec):                 are downloaded locally and cached.

scaleway_server.k8s_master (remote-exec):       If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
scaleway_server.k8s_master (remote-exec):           - 'systemctl status kubelet'
scaleway_server.k8s_master (remote-exec):           - 'journalctl -xeu kubelet'

scaleway_server.k8s_master (remote-exec):       Additionally, a control plane component may have crashed or exited when started by the container runtime.
scaleway_server.k8s_master (remote-exec):       To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
scaleway_server.k8s_master (remote-exec):       Here is one example how you may list all Kubernetes containers running in docker:
scaleway_server.k8s_master (remote-exec):           - 'docker ps -a | grep kube | grep -v pause'
scaleway_server.k8s_master (remote-exec):           Once you have found the failing container, you can inspect its logs with:
scaleway_server.k8s_master (remote-exec):           - 'docker logs CONTAINERID'
scaleway_server.k8s_master (remote-exec): couldn't initialize a Kubernetes cluster

Error: Error applying plan:

1 error(s) occurred:

* scaleway_server.k8s_master: error executing "/tmp/terraform_1537700471.sh": Process exited with status 1

Terraform does not automatically rollback in the face of errors.

Terraform version: 0.11.10 env: arm

[stefanprodan]

duplicate of #20

[stefanprodan]

Fixed by #38