Rook:Timeout过期等待连接/挂载pod的卷

时间:2018-02-18 04:55:36

标签: kubernetes rook-storage

k8s版本:v1.9
环境:VirtualBox
os:Coreos

它是1节点Kubernetes集群 我按照以下步骤操作:

  1. 关注https://rook.io/docs/rook/v0.5/k8s-pre-reqs.html并使用

    更新了kubelet

    环境=" RKT_OPTS = - 体积modprobe,kind = host,source = / usr / sbin / modprobe \
      --mount volume = modprobe,target = / usr / sbin / modprobe \
      --volume lib-modules,kind = host,source = / lib / modules \
      --mount volume = lib-modules,target = / lib / modules \
      --uuid文件保存=的/ var /运行/ kubelet-pod.uuid"

  2. 已安装的ceph实用程序

    rbd -v
    ceph版本10.2.2(45107e21c568dd033c2f0a3107dec8f0b0e58374)

  3. 所有白痴播客都在工作,但是MySQL播放器失败,出现错误'超时已过期,等待播放附加/挂载播放器的容量'

    ➜  kubectl get pod -n rook-system
    NAME                             READY     STATUS    RESTARTS   AGE
    rook-agent-rqw6j                 1/1       Running   0          21m
    rook-operator-5457d48c94-bhh2z   1/1       Running   0          22m
    ➜   kubectl get pod -n rook
    NAME                             READY     STATUS    RESTARTS   AGE
    rook-api-848df956bf-fhmg2        1/1       Running   0          20m
    rook-ceph-mgr0-cfccfd6b8-8brxz   1/1       Running   0          20m
    rook-ceph-mon0-xdd77             1/1       Running   0          21m
    rook-ceph-mon1-gntgh             1/1       Running   0          20m
    rook-ceph-mon2-srmg8             1/1       Running   0          20m
    rook-ceph-osd-84wmn              1/1       Running   0          20m
    ➜   kubectl get pv
    NAME                                       CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS    CLAIM                    STORAGECLASS   REASON    AGE
    pvc-6a4c5c2a-127d-11e8-a846-080027b424ef   20Gi       RWO           Delete          Bound     default/mysql-pv-claim   rook-block               15m
    ➜  kubectl get pvc
    NAME             STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS   AGE
    mysql-pv-claim   Bound     pvc-6a4c5c2a-127d-11e8-a846-080027b424ef   20Gi       RWO           rook-block     15m
    kubectl get pods
    NAME                               READY     STATUS              RESTARTS   AGE
    wordpress-mysql-557ffc4f69-8zxsq   0/1       ContainerCreating   0          16m
    
    
    Error when I describe pod : FailedMount Unable to mount volumes for pod "wordpress-mysql-557ffc4f69-8zxsq_default(6a932df1-127d-11e8-a846-080027b424ef)": timeout expired waiting for volumes to attach/mount for pod "default"/"wordpress-mysql-557ffc4f69-8zxsq". list of unattached/unmounted volumes=[mysql-persistent-storage]
    

    还将以下选项添加到rook-operator.yaml

    - name: FLEXVOLUME_DIR_PATH
      value: "/var/lib/kubelet/volumeplugins"
    

    你能帮忙吗?如果您需要更多详细信息,请与我们联系。我检查了类似的问题,但解决方案无效。

1 个答案:

答案 0 :(得分:0)

您是否使用cephfs或rbd卷作为Ceph的后端?以下是一些要检查的事项:

  1. 请确认您的Pod可以很好地与ceph群集通信,这看起来与您尝试使用的ceph卷的通信存在问题。

  2. 检查您的Ceph音量插件是否设置正确。

  3. # kubectl get pv的状态是什么?

  4. 查看您的持续卷和声明。

  5. 您也可以尝试Root.io工具,它们与Ceph对象存储有很好的集成。