Open charnet1019 opened 3 weeks ago
Hi,
Could you provide more details on the persistence storage you are using? It seems there is some sort of incompatibility with the PVCs created with your storage provider.
Use rancher local sc.
$ kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
local (default) openebs.io/local Delete WaitForFirstConsumer false 23d
local-path rancher.io/local-path Delete WaitForFirstConsumer false 22d
managed-nfs-storage k8s-sigs.io/nfs-subdir-external-provisioner Delete Immediate true 9d
$ kubectl get pvc -n test
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-mysql-qxaymx-0 Bound pvc-31e672da-ebbc-4a7b-be49-d368c41becd6 8Gi RWO local-path 23h
Could you try using other kind of storage-class for the PVC ? I think the issue is due to this. Also, could you check rancher logs and check if there is some errors on this regards. Maybe there is some hint there.
Name and Version
bitnami/mysql 9.23.0
What architecture are you using?
amd64
What steps will reproduce the bug?
/opt/bitnami/scripts/mysql/entrypoint.sh /opt/bitnami/scripts/mysql/run.sh
Are you using any custom parameters or values?
What is the expected behavior?
mysql start success.
What do you see instead?
Additional information
No response