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

failed to list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io) #2767

Open
rptaylor opened this issue Feb 10, 2025 · 0 comments

Comments

@rptaylor
Copy link
Contributor

A default deployment of cinder CSI results in constant errors in logs:

csi-snapshotter W0210 21:36:23.865665       1 reflector.go:424] github.com/kubernetes-csi/external-snapshotter/client/v6/informers/externalversions/factory.go:117: failed to
 list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)                                       
csi-snapshotter E0210 21:36:23.865719       1 reflector.go:140] github.com/kubernetes-csi/external-snapshotter/client/v6/informers/externalversions/factory.go:117: Failed to
 watch *v1.VolumeSnapshotContent: failed to list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s
.io)         

IIUC, some other component (CRDs and/or https://github.com/kubernetes-csi/external-snapshotter ?) need to be installed for this to work.
If the cinder-CSI chart does not install them by default, shouldn't the csi-snapshotter container be disabled by default (via helm value) to avoid wasting resources and producing spurious errors?

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

1 participant