Skip to main content
NetApp Knowledge Base

Numerous unusable Trident Snapshots remain behind since upgrade

Views:
33
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

 

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?