rook: CephFS creation with external cluster results in failures

Is this a bug report or feature request?

Bug Report

Deviation from expected behavior:

In the Ceph UI we do find an entry under “filesystems”

W0812 10:28:26.719870 1 controller.go:943] Retrying syncing claim "96e6b191-152d-4869-94a3-aad45b910c9d", failure 10
E0812 10:28:26.719921 1 controller.go:966] error syncing claim "96e6b191-152d-4869-94a3-aad45b910c9d": failed to provision volume with StorageClass "rook-ceph-cephfs": rpc error: code = DeadlineExceeded desc = context deadline exceeded
I0812 10:28:26.720024 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"tests", Name:"cephfs-storage-claim", UID:"96e6b191-152d-4869-94a3-aad45b910c9d", APIVersion:"v1", ResourceVersion:"100750026", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "rook-ceph-cephfs": rpc error: code = DeadlineExceeded desc = context deadline exceeded

Expected behavior:

How to reproduce it (minimal and precise): Apply config, create pvc.

File(s) to submit:

Configs: https://gist.github.com/electrical/9bc16361faa024d5a89eac9ddd1505bc

Environment:

OS (e.g. from /etc/os-release): Ubuntu
Kernel (e.g. uname -a): 5.4.0-74
Rook version (use rook version inside of a Rook Pod): 1.6.4
Storage backend version (e.g. for ceph do ceph -v): 15.2.13
Kubernetes version (use kubectl version): 1.19.10

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 28 (8 by maintainers)

Most upvoted comments

@travisn @Madhu-1 it works! We’ve created the CephFilesystem on the storage cluster and then the StorageClass on the compute clusters for 2 different environments. Everything now works as expected.

I think it would be good to clarify this in the documentation when it comes to using external clusters for cephfs.

Thank you all so much for your assistance!

electrical on Mar 9, 2022

We haven’t tried it in this specific way. Will give this a try and report back

electrical on Mar 4, 2022