Skip to main content
NetApp Stage KB

Creating a snapshot on Trident storage causes errors and an unusable snapshot

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

 

 

Applies to

Trident for Kubernetes/Openshift

Issue

On a fresh Trident install or after a Kubernetes Upgrade to 1.20 or higher, when attempting to create a Snapshot using kubectl on Trident provisioned PV, the following error occurs:
E0929 16:12:43.790411 1  reflector.go:127] github.com/kubernetes-csi/external-snapshotter/client/v3/informers/externalversions/factory.go:117:
Failed to watch *v1beta1.VolumeSnapshot: failed to list *v1beta1.VolumeSnapshot: the server could not find the requested resource
(get volumesnapshots.snapshot.storage.k8s.io)
 
The snapshot controller is shown as running:
$ kubectl -n kube-system get pod snapshot-controller-0
NAME                    READY   STATUS    RESTARTS   AGE
snapshot-controller-0   1/1     Running   0          43h

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.