Skip to main content
NetApp Knowledge Base

Cluster wide pod rebuild from Kubernetes causes Trident's operator to become unusable

Views:
166
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • Trident 20.07.0, 20.10.0
  • Openshift 4.5.13, 4.5.18
  • Kubernetes 1.18

Issue

Since the pods are destroyed and created in a non-predetermined order, the orchestrator may find missing pods and attempt repair before the whole rebuild is finished.
 
The main error that can comes up during this is:
Warning FailedMount pod/trident-csi-<POD_ID> MountVolume.SetUp failed for volume "trident-csi-token-<POD_ID>" : secret "trident-csi-token-<POD_ID>" not found

 

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