Unable to bound PV for mysql cluster 3 members.

[slipu120]

Is this a BUG REPORT or FEATURE REQUEST?

YES
Choose one: BUG REPORT or FEATURE REQUEST

Versions

MySQL Operator Version:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

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:

• ReadWriteMany
  capacity:
  storage: 10Gi
  hostPath:
  path: /Users/sr_sahani/data1
  persistentVolumeReclaimPolicy: Recycle
  storageClassName: manual

---

apiVersion: mysql.oracle.com/v1
kind: MySQLCluster
metadata:
name: mysql
spec:
members: 3
volumeClaimTemplate:
metadata:
name: data
spec:
storageClassName: manual
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Gi

Anything else we need to know?

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 %