You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
1、Rainbond on k3s(default sc is rook-cephfs) cann't mount the volume
2、Rainbond on k3s(default sc is rook-cephfs) cann't fount the rook-cephfs sc
the status of mysql component is starting,the status of the instance is not ready。
the error in logs of rbd-worker is: ,so we change the storage_class_detail attribution by: alter table tenant_services_volume_type modify storage_class_detail varchar(8192); ,the we can see the rook-cephfs in table tenant_services_volues_type
and we can see the rook-ceph sc on the web
but the status of volume is unmount
Describe the bug
1、Rainbond on k3s(default sc is rook-cephfs) cann't mount the volume
2、Rainbond on k3s(default sc is rook-cephfs) cann't fount the rook-cephfs sc
To Reproduce
Steps to reproduce the behavior:
deploy k3s (single host -172.25.5.108、cluster+ceph--172.24.4.155-172.24.4.158)and ceph (reference by:https://note.youdao.com/s/ZLaETVnV)
deploy rainbond on the singlehost k3s (reference by:https://note.youdao.com/s/86umr0vn),than add the cluster (k3s-cluster-155) with parameters: --set Cluster.RWX.enable=true --set Cluster.RWX.config.storageClassName=rook-cephfs --set Cluster.RWO.enable=true --set Cluster.RWO.storageClassName=rook-cephfs
deploy a app on the k3s-cluster-155 cluster: refercen by:https://www.rainbond.com/docs/quick-start/getting-started
the status of mysql component is starting,the status of the instance is not ready。
the error in logs of rbd-worker is:
,so we change the storage_class_detail attribution by: alter table tenant_services_volume_type modify storage_class_detail varchar(8192); ,the we can see the rook-cephfs in table tenant_services_volues_type
and we can see the rook-ceph sc on the web
but the status of volume is unmount
cat << EOF | kubectl create -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: storagetest11
namespace: bb382d68f0284280acacd9ffca6823c5
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: rainbondsssc
EOF
the error log of rbd-worker likes this:
time="2023-02-13T13:48:20+08:00" level=info msg="provision "bb382d68f0284280acacd9ffca6823c5/storagetest11" class "rainbondsssc": started"
time="2023-02-13T13:48:20+08:00" level=info msg="Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"bb382d68f0284280acacd9ffca6823c5", Name:"storagetest11", UID:"9f370af3-d4a8-400d-8ed6-6d61d54941d8", APIVersion:"v1", ResourceVersion:"3214286", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "bb382d68f0284280acacd9ffca6823c5/storagetest11""
time="2023-02-13T13:48:20+08:00" level=warning msg="Retrying syncing claim "bb382d68f0284280acacd9ffca6823c5/storagetest11" because failures 0 < threshold 15"
E0213 13:48:20.664989 1 controller.go:693] error syncing claim "bb382d68f0284280acacd9ffca6823c5/storagetest11": failed to provision volume with StorageClass "rainbondsssc": can not parse volume id
time="2023-02-13T13:48:20+08:00" level=info msg="Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"bb382d68f0284280acacd9ffca6823c5", Name:"storagetest11", UID:"9f370af3-d4a8-400d-8ed6-6d61d54941d8", APIVersion:"v1", ResourceVersion:"3214286", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "rainbondsssc": can not parse volume id"
Screenshots
If applicable, add screenshots to help explain your problem.
The relevant information:
The text was updated successfully, but these errors were encountered: