Jx: Fails to create minikube cluster

[tonsV2]

Summary

Fails to create minikube cluster

I did "kubectl delete clusterrolebinding add-on-cluster-admin" to fix the role binding issue. However then I get:

>>> jx create cluster minikube --verbose
an existing Minikube cluster is already running, perhaps use `jx install`.
Note existing Minikube must have RBAC enabled, running `minikube delete` and `jx create cluster minikube` creates a new VM with RBAC enabled

Steps to reproduce the behavior

>>> jx create cluster minikube --verbose
? memory (MB) 4096
? cpu (cores) 3
? disk-size (MB) 150GB
? Select driver: virtualbox
We cannot yet automate the installation of VirtualBox - can you install this manually please?
Please see: https://www.virtualbox.org/wiki/Downloads
Creating Minikube cluster...
I1113 22:32:12.522692     663 notify.go:121] Checking for updates...
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
I1113 22:32:12.674497     663 utils.go:100] retry loop 0
I1113 22:32:12.674567     663 cluster.go:69] Machine does not exist... provisioning new machine
I1113 22:32:12.674589     663 cluster.go:70] Provisioning machine with config: {MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v0.30.0.iso Memory:4096 CPUs:3 DiskSize:150000 VMDriver:virtualbox HyperkitVpnKitSock: HyperkitVSockPorts:[] XhyveDiskDriver:ahci-hd DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KvmNetwork:default Downloader:{} DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: GPU:false}
I1113 22:32:12.674703     663 downloader.go:56] Not caching ISO, using https://storage.googleapis.com/minikube/iso/minikube-v0.30.0.iso
Downloading /home/tons/.minikube/cache/boot2docker.iso from file:///home/tons/.minikube/cache/iso/minikube-v0.30.0.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting the VM...
Check network to re-create if needed...
Waiting for an IP...
I1113 22:36:58.755844     663 utils.go:100] retry loop 0
I1113 22:37:00.461367     663 ssh_runner.go:57] Run: sudo rm -f /etc/docker/ca.pem
I1113 22:37:00.479289     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I1113 22:37:00.522277     663 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server.pem
I1113 22:37:00.538713     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
I1113 22:37:00.574519     663 ssh_runner.go:57] Run: sudo rm -f /etc/docker/server-key.pem
I1113 22:37:00.593675     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/docker
Setting Docker configuration on the remote daemon...
Getting VM IP address...
Moving files into cluster...
I1113 22:37:04.089296     663 kubeadm.go:220] Container runtime flag provided with no value, using defaults.
I1113 22:37:04.089540     663 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubeadm
I1113 22:37:04.089612     663 ssh_runner.go:57] Run: sudo rm -f /usr/bin/kubelet
I1113 22:37:04.110751     663 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I1113 22:37:04.114799     663 ssh_runner.go:57] Run: sudo mkdir -p /usr/bin
I1113 22:37:17.624659     663 ssh_runner.go:57] Run: sudo rm -f /lib/systemd/system/kubelet.service
I1113 22:37:17.641034     663 ssh_runner.go:57] Run: sudo mkdir -p /lib/systemd/system
I1113 22:37:17.683888     663 ssh_runner.go:57] Run: sudo rm -f /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
I1113 22:37:17.704691     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/systemd/system/kubelet.service.d
I1113 22:37:17.742703     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/kubeadm.yaml
I1113 22:37:17.762808     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib
I1113 22:37:18.001629     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-controller.yaml
I1113 22:37:18.017655     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.055586     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-configmap.yaml
I1113 22:37:18.074515     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.119094     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-svc.yaml
I1113 22:37:18.144762     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.195629     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-crbinding.yaml
I1113 22:37:18.223633     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.267866     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-sa.yaml
I1113 22:37:18.286537     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.332544     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/coreDNS-clusterrole.yaml
I1113 22:37:18.349600     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.387724     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-configmap.yaml
I1113 22:37:18.412684     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.455744     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-rbac.yaml
I1113 22:37:18.473670     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.522548     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-dp.yaml
I1113 22:37:18.541691     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.578759     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/ingress-svc.yaml
I1113 22:37:18.602086     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.643670     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/manifests/addon-manager.yaml
I1113 22:37:18.661532     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/manifests/
I1113 22:37:18.701615     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storage-provisioner.yaml
I1113 22:37:18.720214     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.756217     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/storageclass.yaml
I1113 22:37:18.774934     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.820392     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-dp.yaml
I1113 22:37:18.838646     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.878954     663 ssh_runner.go:57] Run: sudo rm -f /etc/kubernetes/addons/dashboard-svc.yaml
I1113 22:37:18.904596     663 ssh_runner.go:57] Run: sudo mkdir -p /etc/kubernetes/addons
I1113 22:37:18.939675     663 ssh_runner.go:57] Run: 
sudo systemctl daemon-reload &&
sudo systemctl enable kubelet &&
sudo systemctl start kubelet

Setting up certs...
I1113 22:37:19.420981     663 certs.go:47] Setting up certificates for IP: 192.168.99.100
I1113 22:37:19.476216     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/ca.crt
I1113 22:37:19.494684     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.535726     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/ca.key
I1113 22:37:19.557997     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.599007     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/apiserver.crt
I1113 22:37:19.619752     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.667794     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/apiserver.key
I1113 22:37:19.686640     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.728360     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/proxy-client-ca.crt
I1113 22:37:19.753999     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.799761     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/proxy-client-ca.key
I1113 22:37:19.819718     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.865671     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/proxy-client.crt
I1113 22:37:19.884559     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:19.928639     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/certs/proxy-client.key
I1113 22:37:19.956712     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube/certs/
I1113 22:37:20.005046     663 ssh_runner.go:57] Run: sudo rm -f /var/lib/minikube/kubeconfig
I1113 22:37:20.024896     663 ssh_runner.go:57] Run: sudo mkdir -p /var/lib/minikube
Connecting to cluster...
Setting up kubeconfig...
I1113 22:37:20.751871     663 config.go:125] Using kubeconfig:  /home/tons/.kube/config
Starting cluster components...
I1113 22:37:20.759709     663 ssh_runner.go:80] Run with output: 
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  &&
sudo /usr/bin/kubeadm alpha phase addon kube-dns

I1113 22:38:51.123334     663 utils.go:100] retry loop 0
Kubectl is now configured to use the cluster.
Loading cached images from config file.
Minikube cluster created.
clusterrolebinding.rbac.authorization.k8s.io/add-on-cluster-admin created
Initialising cluster ...
Using helmBinary helm with feature flag: none
Namespace jx created 
 set exposeController Config Domain 192.168.99.100.nip.io
Storing the kubernetes provider minikube in the TeamSettings
Updated the team settings in namespace jx
Git configured for user: xxx and email [email protected]
Trying to create ClusterRoleBinding minikube-cluster-admin-binding for role: cluster-admin for user minikube
 clusterrolebindings.rbac.authorization.k8s.io "minikube-cluster-admin-binding" not found
Created ClusterRoleBinding minikube-cluster-admin-binding
Using helm2
Configuring tiller
Created ServiceAccount tiller in namespace kube-system
Trying to create ClusterRoleBinding tiller for role: cluster-admin and ServiceAccount: kube-system/tiller
Created ClusterRoleBinding tiller
Initialising helm using ServiceAccount tiller in namespace kube-system
Using helmBinary helm with feature flag: none
Waiting for tiller-deploy to be ready in tiller namespace kube-system
helm installed and configured
nginx ingress controller already enabled
Lets set up a Git username and API token to be able to perform CI/CD

? GitHub username for CI/CD pipelines: tonsv2
error creating cluster cannot work out if this is a prow based install: no environment with name 'dev' found

Jx version

Using helmBinary helm with feature flag: none
NAME               VERSION
jx                 1.3.560
Kubernetes cluster v1.10.0
kubectl            v1.12.2
helm client        v2.11.0+g2e55dbe
helm server        v2.11.0+g2e55dbe
git                git version 2.19.1

Kubernetes cluster

Just minikube

Operating system / Environment

Fedora 29

Expected behavior

The cluster should spawn

Actual behavior

It exits with the following error:
error creating cluster cannot work out if this is a prow based install: no environment with name 'dev' found

[wbrefvem]

@tonsV2 It looks like you've already got minikube installed and running, in which case you wouldn't need to create a new minikube cluster. Can you post the output of the following?

minikube status

[tonsV2]

@wbrefvem Thanks for the reply! I did a minikube delete before running the jx command. However after adding rm -rf ~/.minikube to the mix it works.