Kubernetes 无法使用StorageClass设置卷；“快速rbd”；

我正在使用RBD客户端与ceph和kubernetes进行通信。我已经创建了PVC“myclaim”，它长期处于待定状态。我得到下面的例外。 我猜这可能是因为它可能试图从ceph jewel映射rbd图像，或者可能没有获得钥匙圈。 请查看以下例外情况并提供适当建议。 如果有人知道“如何通过外部供应器“ceph.com/rbd”或手动创建persistentvolume controller”，请分享您的观点

例外情况：

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.

---

将OP的评论作为答案发布（社区维基）：

我得到的问题与持续的批量索赔有关，我只是 更改yml文件中的“名称”，即在yml文件中指定名称 使用一些xyz（您要指定的pod名称）数据 确保所有名称都应相同，并删除storageclass。 问题解决了

---

你能和我们分享你的StorageClass配置吗？我参考了。请完成此操作，您将在此处获得Storageclass配置。请编辑您的问题以获得更好的可见性。此外，请提供有关您使用的版本的信息。是否存在以下任何文件

/etc/ceph/ceph.conf

，

/root/.ceph/ceph.conf

或

ceph.conf

听起来像是卷配置失败了，因为如果没有我使用的config.ceph版本，就无法使用ceph