Description

Expected Behavior

it should just work ;^) But if not it needs to feed the errored state back somehow. 
in this case it probably needs to say that the disk is already mounted. 

## Current Behavior
<!-- Tell us what happens instead -->
Repro'ed:

 bmath@timesink:~/maya/gke/test86$ cat cassandra-localpv-storageClass.yaml
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
   name: cassandra-device
   annotations:
     openebs.io/cas-type: local
     cas.openebs.io/config: |
       - name: FSType
         value: xfs
 provisioner: openebs.io/local
 volumeBindingMode: WaitForFirstConsumer
 reclaimPolicy: Delete
 
 bmath@timesink:~/maya/gke/test86$ kubectl apply -f cassandra-
 cassandra-localpv-storageClass.yaml  cassandra-stress-job.yaml            

 bmath@timesink:~/maya/gke/test86$ kubectl apply -f cassandra-localpv-storageClass.yaml 
 storageclass.storage.k8s.io/cassandra-device created

 bmath@timesink:~/maya/gke/test86$ ./install_cassandra
 NAME:   cassandra
 LAST DEPLOYED: Mon Feb 17 14:08:47 2020
 NAMESPACE: cassandra
 STATUS: DEPLOYED
 
 RESOURCES:
 ==> v1/Pod(related)
 NAME         READY  STATUS             RESTARTS  AGE
 cassandra-0  0/1    ContainerCreating  0         0s
 
 ==> v1/Service
 NAME       TYPE       CLUSTER-IP  EXTERNAL-IP  PORT(S)                                       AGE
 cassandra  ClusterIP  None        <none>       7000/TCP,7001/TCP,7199/TCP,9042/TCP,9160/TCP  0s
 
 ==> v1/StatefulSet
 NAME       READY  AGE
 cassandra  0/3    0s
 
 
 NOTES:
 Cassandra CQL can be accessed via port 9042 on the following DNS name from within your cluster:
 Cassandra Thrift can be accessed via port 9160 on the following DNS name from within your cluster:
 
 If you want to connect to the remote instance with your local Cassandra CQL cli. To forward the API port to localhost:9042 run the following:
 - kubectl port-forward --namespace cassandra $(kubectl get pods --namespace cassandra -l app=cassandra,release=cassandra -o jsonpath='{ .items[0].metadata.name }') 9042:9042
 
 If you want to connect to the Cassandra CQL run the following:
 - kubectl port-forward --namespace cassandra $(kubectl get pods --namespace cassandra -l "app=cassandra,release=cassandra" -o jsonpath="{.items[0].metadata.name}") 9042:9042
   echo cqlsh 127.0.0.1 9042
 
 You can also see the cluster status by run the following:
 - kubectl exec -it --namespace cassandra $(kubectl get pods --namespace cassandra -l app=cassandra,release=cassandra -o jsonpath='{.items[0].metadata.name}') nodetool status
 
 To tail the logs for the Cassandra pod run the following:
 - kubectl logs -f --namespace cassandra $(kubectl get pods --namespace cassandra -l app=cassandra,release=cassandra -o jsonpath='{ .items[0].metadata.name }')
 
 bmath@timesink:~/maya/gke/test86$ kubectl get bd -A
 NAMESPACE   NAME                                           NODENAME                                      SIZE           CLAIMSTATE   STATUS   AGE
 openebs     blockdevice-1a89fd1f4bc1fedbfb268e91812b3ad3   gke-bmath-test86-default-pool-2134831e-703r   402653184000   Unclaimed    Active   3h54m
 openebs     blockdevice-8e45b547a555278739ab6db31d9ed7a9   gke-bmath-test86-default-pool-de467c51-pqtg   402653184000   Unclaimed    Active   3h54m
 openebs     blockdevice-e79e3a47c2e5ce23074a8df30d735e88   gke-bmath-test86-default-pool-fb0d6073-q14n   402653184000   Unclaimed    Active   3h54m

 bmath@timesink:~/maya/gke/test86$ kubectl get pvc -n cassandra 
 NAME               STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS       AGE
 data-cassandra-0   Bound    pvc-b138c5ac-519b-11ea-b47f-42010a800196   10Gi       RWO            cassandra-device   3h29m
 data-cassandra-1   Bound    pvc-fcb08dfa-519b-11ea-b47f-42010a800196   10Gi       RWO            cassandra-device   3h27m
 data-cassandra-2   Bound    pvc-44c8250c-519c-11ea-b47f-42010a800196   10Gi       RWO            cassandra-device   3h25m


## Possible Solution
<!-- Suggest a fix or reason for this bug -->

Produce an actionable error appearing maybe in describe sc events list or 
some other likely place to check, and prevent the pod from just running on the root fs.