rook: Bug: CSI subvolumegroup is not created by rook automatically

• Bug Report In continuation of https://github.com/rook/rook/issues/4006 Rook does not create the expected subvolumegroup called “csi” when creating a new filesystem.

Deviation from expected behavior:

csi driver is not creating the subvolumegroup called csi

Expected behavior: csi driver should create the subvolumegroup called csi

How to reproduce it (minimal and precise):

Create a CephFilesystem with the following: https://github.com/rook/rook/blob/master/cluster/examples/kubernetes/ceph/filesystem.yaml

Afterwards, create a storageclass “rook-cephfs” which makes use the filesystem called “myfs” created above. https://github.com/rook/rook/blob/master/cluster/examples/kubernetes/ceph/csi/cephfs/storageclass.yaml

Lastly, create the PVC and test deployment https://github.com/rook/rook/blob/master/cluster/examples/kubernetes/ceph/csi/cephfs/kube-registry.yaml

File(s) to submit:

All files as per links above.

Environment:

• OS (e.g. from /etc/os-release): Centos 7
• Kernel (e.g. uname -a):
• Cloud provider or hardware configuration:. VMWare bare metal
• Rook version (use rook version inside of a Rook Pod): version 1.4
• Storage backend version (e.g. for ceph do ceph -v): ceph/ceph:v15.2.4
• Kubernetes version (use kubectl version): 1.8
• Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift): Kubernetes on bare metal
• Storage backend status (e.g. for Ceph use ceph health in the [Rook Ceph toolbox]. Health ok