gluster / gluster-kubernetes

GlusterFS Native Storage Service for Kubernetes
Apache License 2.0
874 stars 390 forks source link

unable to continue installation after failure #616

Open poligraph opened 4 years ago

poligraph commented 4 years ago

if any error occurs during gk-deploy command it's unable to re-run command again

for example, if I run second time ./gk-deploy -g --admin-key 123456 --user-key 123456

I will get following error and I don't know how to continue installation.

/usr/bin/kubectl -n default exec -i deploy-heketi-6ff89c7498-zpn27 -- heketi-cli -s http://localhost:8080 --user admin --secret '123456' topology load --json=/etc/heketi/topology.json 2>&1
Found node node1 on cluster a850dff669c2c42cfc18c9a58b0cdbfd
Found device /dev/sdb
Found node node2 on cluster a850dff669c2c42cfc18c9a58b0cdbfd
Found device /dev/sdb
Found node node3 on cluster a850dff669c2c42cfc18c9a58b0cdbfd
Found device /dev/sdb
heketi topology loaded.
/usr/bin/kubectl -n default exec -i deploy-heketi-6ff89c7498-zpn27 -- heketi-cli -s http://localhost:8080 --user admin --secret '123456' setup-openshift-heketi-storage --listfile=/tmp/heketi-storage.json  2>&1
Error: Volume heketidbstorage alreay exists
command terminated with exit code 255
Failed on setup openshift heketi storage
This may indicate that the storage must be wiped and the GlusterFS nodes must be reset.
piotrgo commented 4 years ago

You could comment out section in the gk-deploy script that does all the steps that have been successful in your case and re-run from line 875: eval_output "${CLI} exec -i ${heketi_pod} -- cat /tmp/heketi-storage.json