none: error uploading configuration: unable to create configmap:server sent GOAWAY and closed the connection

[tstromberg]

Appears to be a new flaky behavior with v1.12 of Kubernetes:

https://storage.googleapis.com/minikube-builds/logs/3487/Linux-None.txt

 00:48:05 | ! E1222 00:48:05.360538   20582 start.go:343] Error starting cluster:  kubeadm init error 
 00:48:05 | ! sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI 
 00:48:05 | !  running command: : running command: 
 00:48:05 | ! sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI 
 00:48:05 | !  output: [init] using Kubernetes version: v1.12.4
 00:48:05 | ! [preflight] running pre-flight checks
 00:48:05 | ! 	[WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
 00:48:05 | ! 	[WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
 00:48:05 | ! 	[WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
 00:48:05 | ! 	[WARNING FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
 00:48:05 | ! 	[WARNING FileExisting-socat]: socat not found in system path
 00:48:05 | ! 	[WARNING Hostname]: hostname "minikube" could not be reached
 00:48:05 | ! 	[WARNING Hostname]: hostname "minikube" lookup minikube on 169.254.169.254:53: no such host
 00:48:05 | ! 	[WARNING Port-10250]: Port 10250 is in use
 00:48:05 | ! 	[WARNING DirAvailable--data-minikube]: /data/minikube is not empty
 00:48:05 | ! [preflight/images] Pulling images required for setting up a Kubernetes cluster
 00:48:05 | ! [preflight/images] This might take a minute or two, depending on the speed of your internet connection
 00:48:05 | ! [preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
 00:48:05 | ! [kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
 00:48:05 | ! [kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
 00:48:05 | ! [preflight] Activating the kubelet service
 00:48:05 | ! [certificates] Using the existing apiserver certificate and key.
 00:48:05 | ! [certificates] Using the existing apiserver-kubelet-client certificate and key.
 00:48:05 | ! [certificates] Using the existing etcd/server certificate and key.
 00:48:05 | ! [certificates] Using the existing etcd/peer certificate and key.
 00:48:05 | ! [certificates] Using the existing etcd/healthcheck-client certificate and key.
 00:48:05 | ! [certificates] Using the existing apiserver-etcd-client certificate and key.
 00:48:05 | ! [certificates] Using the existing front-proxy-client certificate and key.
 00:48:05 | ! [certificates] valid certificates and keys now exist in "/var/lib/minikube/certs/"
 00:48:05 | ! [certificates] Using the existing sa key.
 00:48:05 | ! [kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/admin.conf"
 00:48:05 | ! [kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/kubelet.conf"
 00:48:05 | ! [kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/controller-manager.conf"
 00:48:05 | ! [kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/scheduler.conf"
 00:48:05 | ! [controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
 00:48:05 | ! [controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
 00:48:05 | ! [controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
 00:48:05 | ! [etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
 00:48:05 | ! [init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests" 
 00:48:05 | ! [init] this might take a minute or longer if the control plane images have to be pulled
 00:48:05 | ! [apiclient] All control plane components are healthy after 7.491292 seconds
 00:48:05 | ! [uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
 00:48:05 | ! error uploading configuration: unable to create configmap: Post https://localhost:8443/api/v1/namespaces/kube-system/configmaps: http2: server sent GOAWAY and closed the connection; LastStreamID=9, ErrCode=NO_ERROR, debug=""

[tstromberg]

I think this is a flake in TestStartStop. Probably due to the none driver incompletely implementing stop.