oracle / mysql-operator

Create, operate and scale self-healing MySQL clusters in Kubernetes
870 stars 235 forks source link

Unable to bound PV for mysql cluster 3 members. #296

Open slipu120 opened 5 years ago

slipu120 commented 5 years ago

Is this a BUG REPORT or FEATURE REQUEST?

YES Choose one: BUG REPORT or FEATURE REQUEST

Versions

MySQL Operator Version:

Environment:

What happened?

Unable to bound PV for mysql cluster 3 members.

What you expected to happen?

3 members should come up with PV

How to reproduce it (as minimally and precisely as possible)?


apiVersion: v1 kind: PersistentVolume metadata: labels: type: local name: mysql-local-volume spec: accessModes:

errors: sr_sahani@soumyas-MacBook-Pro data % kubectl get pods NAME READY STATUS RESTARTS AGE mysql-cluster-with-volume-0 2/2 Running 0 3h15m mysql-cluster-with-volume-1 0/2 Pending 0 3h14m sr_sahani@soumyas-MacBook-Pro data % kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE mysql-local-volume 10Gi RWX Recycle Bound default/data-mysql-cluster-with-volume-0 manual 21h sr_sahani@soumyas-MacBook-Pro data % kubectl describe pods mysql-cluster-with-volume-1 Events: Type Reason Age From Message


Warning FailedScheduling 4m1s (x130 over 3h14m) default-scheduler pod has unbound immediate PersistentVolumeClaims sr_sahani@soumyas-MacBook-Pro data %