Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploying Vistio-API fails with 'PersistentVolumeClaim is not bound: "vistio-db-vistio-api-0" (repeated 4 times)' #8

Open
garysu opened this issue Jul 7, 2018 · 12 comments

Comments

@garysu
Copy link

garysu commented Jul 7, 2018

The PVC claim just sits in a pending state and at API doesn't come up successfully, the Web UI just sits there "Loading".

kubectl version shows:
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

@nmnellis
Copy link
Owner

Where is your Kubernetes cluster deployed? Vistio by default assumes that you have a Kubernetes StorageClass named standard
Example of mine

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: standard
parameters:
  type: gp2
provisioner: kubernetes.io/aws-ebs

@garysu
Copy link
Author

garysu commented Jul 17, 2018 via email

@garysu
Copy link
Author

garysu commented Jul 17, 2018 via email

@redstyr
Copy link

redstyr commented Aug 9, 2018

Same error here. K8s deployed with kubeadm.

  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  17s (x3 over 33s)  default-scheduler  pod has unbound PersistentVolumeClaims
kubectl get storageclass -n istio-system local-storage -oyaml          ⎈ isobox:tethering
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  creationTimestamp: 2018-07-03T15:48:22Z
  name: local-storage
  resourceVersion: "601"
  selfLink: /apis/storage.k8s.io/v1/storageclasses/local-storage
  uid: 841bab8a-7ed8-11e8-ac4d-005056950510
provisioner: kubernetes.io/no-provisioner
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

@nmnellis
Copy link
Owner

nmnellis commented Aug 9, 2018

this is more of an issue with statefulsets and pvcs than with vistio. Upgrading your kubernetes version to >=1.9 might help fix this issue

@redstyr
Copy link

redstyr commented Aug 9, 2018

My kube version is v1.10.2

@garysu
Copy link
Author

garysu commented Aug 9, 2018 via email

@nmnellis
Copy link
Owner

maybe follow this? helm/charts#5188 (comment)

@SS-TT
Copy link

SS-TT commented Sep 10, 2018

Same issue for me, but I'm using NFS so I don't have any StorageClass.

@donbowman
Copy link

AKS also does not have 'standard', it has 'default'.

$ kubectl get sc
NAME                PROVISIONER                AGE
default (default)   kubernetes.io/azure-disk   5d
managed-premium     kubernetes.io/azure-disk   38d

@fjudith
Copy link

fjudith commented Nov 29, 2018

Works well with rook.

helm install helm/vistio -f helm/vistio/values-with-ingress.yaml --set api.storage.class=rook-ceph-block --name vistio --namespace default

kubectl -n default get pods,svc,pvc -l app=vistio-api,app=vistio-api -o wide
NAME               READY   STATUS    RESTARTS   AGE   IP           NODE     NOMINATED NODE
pod/vistio-api-0   3/3     Running   0          18m   10.2.240.6   node03   <none>

NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE   SELECTOR
service/vistio-api   ClusterIP   10.3.0.23    <none>        9091/TCP   18m   app=vistio-api,release=vistio

NAME                                           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
persistentvolumeclaim/vistio-db-vistio-api-0   Bound    pvc-b220c7ea-f3ff-11e8-9102-960000143fe3   5Gi        RWO            rook-ceph-block   4h59m

@fjudith
Copy link

fjudith commented Nov 29, 2018

I suggest to not enforce the name of the storageclass.
If left empty ("") PVC will automatically select the (default) storage class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants