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

Rainbond on k3s(default sc is rook-cephfs) cann't mount the volume #1545

Closed
jameswangjz opened this issue Feb 13, 2023 · 1 comment
Closed
Assignees
Labels
kind/bug BUG Feedback
Milestone

Comments

@jameswangjz
Copy link

jameswangjz commented Feb 13, 2023

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:

  1. 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)

  2. 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

  3. deploy a app on the k3s-cluster-155 cluster: refercen by:https://www.rainbond.com/docs/quick-start/getting-started

  4. the status of mysql component is starting,the status of the instance is not ready。
    image
    image

  5. the error in logs of rbd-worker is:
    image,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
    image
    and we can see the rook-ceph sc on the web
    image
    but the status of volume is unmount
    image

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:

  • Rainbond Version [v5.11.0-release-1340c6c32-2023-02-01-06-allinone]
  • k3s [v1.25.5+k3s2]
  • ceph [v1.10.8]
  • Browser [版本 109.0.5414.121(正式版本) (64 位)]
  • os/kernal:Centos7.9/3.10.0-957.el7.x86_64
@ZhangSetSail
Copy link
Collaborator

ZhangSetSail commented Jul 7, 2023

你的第一个问题字短长度过短已经修改,第二个问题看起来不是 Rainbond 的问题,可参考ceph/ceph-csi#3929

@ZhangSetSail ZhangSetSail modified the milestones: 5.13.1, 5.14.3 Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug BUG Feedback
Projects
None yet
Development

No branches or pull requests

4 participants