无法使用 StorageClass“fast-rbd”配置卷答案

【问题标题】：failed to provision volume with StorageClass "fast-rbd"无法使用 StorageClass“fast-rbd”配置卷
【发布时间】：2020-01-15 11:58:52
【问题描述】：

我正在使用 RBD 客户端与 Kubernetes 进行 ceph 通信。我创建了 PVC 'myclaim'，它长期以来一直处于 Pending 状态。我收到以下异常。我猜它可能会发生，因为它可能试图尝试从 ceph Jewel 映射 rbd 图像，或者可能没有得到密钥环。请查看以下异常并提供适当的建议。如果有人知道“如何通过外部供应商“ceph.com/rbd”或手动创建持久卷控制器”，请分享您的观点。

例外：

Normal   Provisioning        39m (x3 over 162m)  ceph.com/rbd_rbd-provisioner-98b88f5d6-q98tf_faed28f5-d621-11e9-9f60-c63a8677257e  External provisioner is provisioning volume for claim "default/myclaim"
  Warning  ProvisioningFailed  39m                 ceph.com/rbd_rbd-provisioner-98b88f5d6-q98tf_faed28f5-d621-11e9-9f60-c63a8677257e  failed to provision volume with StorageClass "fast-rbd": failed to create rbd image: exit status 110, command output: did not load config file, using default settings.
2019-09-13 13:41:50.588 7fc5c40f6900 -1 Errors while parsing config file!
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open /root/.ceph/ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.588 7fc5c40f6900 -1 Errors while parsing config file!
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open /root/.ceph/ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.588 7fc5c40f6900 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2019-09-13 13:41:50.620 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 13:46:50.621 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 13:46:50.621 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 13:51:50.620 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 13:51:50.620 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 13:56:50.622 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 13:56:50.622 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:01:50.624 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:01:50.624 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:06:50.625 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:06:50.625 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:11:50.627 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:11:50.627 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:16:50.628 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:16:50.628 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:21:50.627 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:21:50.627 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:26:50.629 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
2019-09-13 14:26:50.629 7fc5c40f6900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
2019-09-13 14:31:50.631 7fc5c40f6900  0 monclient(hunting): authenticate timed out after 300
rbd: couldn't connect to the cluster!
  Normal  ExternalProvisioning  52s (x1881 over 7h50m)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "ceph.com/rbd" or manually created by system administrator.

【问题讨论】：

您能与我们分享您的 StorageClass 配置吗？
我提到了akomljen.com/…。请通过这里，您将在此处获得 Storageclass 配置。
请编辑您的问题以获得更好的可见性。还请提供有关您使用的版本的信息。
以下文件是否存在？ /etc/ceph/ceph.conf,/root/.ceph/ceph.conf 或 ceph.conf 听起来卷配置失败，因为没有配置就无法使用 ceph。
ceph 版本模仿我正在使用的稳定版

标签： kubernetes ceph

【解决方案1】：

发布 OP 的评论作为答案（社区 wiki）：

我遇到了与 Persistent Volume 声明相关的问题，我只是更改 yml 文件中的“名称”，即在 yml 文件中分配名称带有一些 xyz 的数据（您要指定的 pod 名称），所以确保所有名称都应相同并删除存储类。问题解决了！

【讨论】：