suadhika
commented
4 years ago I forgot to remove label from master which I previously added in the topology.json.sample file and later removed.
Closed suadhika closed 4 years ago
suadhika
commented
4 years ago I forgot to remove label from master which I previously added in the topology.json.sample file and later removed.
While trunning the code sudo ./gk-deploy -g topology.json.sample --admin-key admin --user-key user : it is trying to install node in my master node whereas glusterfs pod is running only at 2 worker node.
Finally I get an error:
Using Kubernetes CLI. Using namespace "default". Checking for pre-existing resources... GlusterFS pods ... not found. deploy-heketi pod ... not found. heketi pod ... not found. gluster-s3 pod ... not found. Creating initial resources ... serviceaccount/heketi-service-account created clusterrolebinding.rbac.authorization.k8s.io/heketi-sa-view created clusterrolebinding.rbac.authorization.k8s.io/heketi-sa-view labeled OK node/test-eu-k8s-k8s-node-nf-1 not labeled node/test-eu-k8s-k8s-node-nf-2 not labeled daemonset.apps/glusterfs created Waiting for GlusterFS pods to start ... OK Error from server (AlreadyExists): secrets "heketi-config-secret" already exists secret/heketi-config-secret not labeled service/deploy-heketi created deployment.apps/deploy-heketi created Waiting for deploy-heketi pod to start ... OK Creating cluster ... ID: 9a8ef0e8b98e84444f1571bc7c132aad Allowing file volumes on cluster. Allowing block volumes on cluster. Creating node test-eu-k8s-k8s-master-nf-1 ... Unable to create node: New Node doesn't have glusterd running Found node test-eu-k8s-k8s-node-nf-1 ... ID: 4ba415758d9420758a0c64218eb71516 Found device /dev/vdb Found node test-eu-k8s-k8s-node-nf-2 ... ID: 05b0509fbd69c104322253fe3275c88c Found device /dev/vdb Error loading the cluster topology. Please check the failed node or device and rerun this script.