Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StorageClass volPrefix has no effect to the volume name #57

Closed
dewongway opened this issue Jan 20, 2023 · 3 comments
Closed

StorageClass volPrefix has no effect to the volume name #57

dewongway opened this issue Jan 20, 2023 · 3 comments
Assignees

Comments

@dewongway
Copy link

Describe the bug
I am not sure what the volPrefix supposed to do. When I set it to csi-me5, I don't see it being taken into consideration for the PVC name, PV name, or the volume name on the storage array.

To Reproduce
Steps to reproduce the behavior:

Set volPrefix in the storageclass and create a PV using the storage class.

apiVersion: storage.k8s.io/v1
kind: StorageClass
provisioner: csi-exos-x.seagate.com
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
metadata:
  name: me5-2-storageclass2
parameters:
  csi.storage.k8s.io/provisioner-secret-name: seagate-exos-x-csi-secrets
  csi.storage.k8s.io/provisioner-secret-namespace: seagate
  csi.storage.k8s.io/controller-publish-secret-name: seagate-exos-x-csi-secrets
  csi.storage.k8s.io/controller-publish-secret-namespace: seagate
  csi.storage.k8s.io/controller-expand-secret-name: seagate-exos-x-csi-secrets
  csi.storage.k8s.io/controller-expand-secret-namespace: seagate
  fsType: ext4
  pool: A
  volPrefix: csi-me5
  storageProtocol: iscsi
$ kubectl get pvc -n test-seagate
NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS          AGE
me5-2-pvc2   Bound    pvc-c1312963-2c5d-4a77-8b71-6d23d541e623   30Gi       RWO            me5-2-storageclass2   5m41s

$ kubectl get pv -n test-seagate
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                     STORAGECLASS                 REASON   AGE
pvc-c1312963-2c5d-4a77-8b71-6d23d541e623   30Gi       RWO            Delete           Bound    test-seagate/me5-2-pvc2   me5-2-storageclass2                   5m20s

image

Expected behavior
I expect to see the prefix as part of the volume name.

Screenshots
If applicable, add screenshots to help explain your problem.

Storage System (please complete the following information):

  • Vendor: Dell PowerVault ME5
  • Model
  • Firmware Version: ME5.1.0.1.0

Environment:

  • Kubernetes version: v1.24.4+rke2r1
  • Host OS: SUSE Linux Enterprise Server 15 SP3

Additional context
Add any other context about the problem here.

@seagate-chris seagate-chris self-assigned this Jan 30, 2023
@seagate-chris
Copy link
Collaborator

Thanks, we're looking into this now.

@seagate-chris
Copy link
Collaborator

The limit for the VolNamePrefix parameter is 3 characters, so your input "csi-me5" was silently truncated to "csi". We'll update the examples and add a warning in the logs to make this clearer.

@dewongway
Copy link
Author

Great. Thanks for the info.

seagate-chris added a commit that referenced this issue Mar 29, 2023
fix: clarify comment for volPrefix in storageclass example (#57)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants