Skip to main content
NetApp Stage KB

Numerous unusable Trident Snapshots remain behind since upgrade

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

 

 

Applies to

  • Trident for Openshift/Kubernetes
  • Kubernetes 1.20

Issue

After an upgrade of Trident and Kubernetes to support Snapshot version 1 (v1), the older v1beta1 Snapshots are not longer usable.
The error message generated is:
E0127 16:19:22.624984       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.0/tools/cache/reflector.go:167: Failed to watch
*v1.TridentVolume: failed to list *v1.TridentVolume: Unauthorized
{"@timestamp":"2022-01-27T16:19:23Z","handler":"AddOrUpdateNode","level":"error","message":"Unauthorized","node":"",
"requestID":"fb5d13a7-63ef-445f-9fa9-d3b60d6d21a6","requestSource":"REST"}
 
New Snapshot are also not possible while Trident is attempting to clean up the old (v1beta1) Snapshots:

Failed to create snapshot content with error snapshot controller failed to update <PV_NAME>/<SNAPSHOT_NAME> on API server:

create not allowed while custom resource definition is terminating

 

 

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.

 

  • Was this article helpful?