Skip to main content
NetApp Knowledge Base

Trident upgrade keeps initializing after having removed a backend from the network

Views:
651
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes/Openshift

Issue

After having removed a backend from the Kubernetes environment, upgrading or reinstalling Trident hangs in initialization:

 

time="2020-07-20T18:00:23Z" level=error msg="API invocation failed. Post \"https://<Storage_mgmt_IP-Address>/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
time="2020-07-20T18:00:23Z" level=error msg="Could not initialize storage driver." error="error initializing ontap-nas-economy driver: could not create Data ONTAP API client: error reading SVM details: Post \"https://<Storage_mgmt_IP-Address>/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
time="2020-07-20T18:00:23Z" level=warning msg="Cannot terminate an uninitialized backend." backend= backendUUID=<UUID> driver=ontap-nas-economy state=failed
time="2020-07-20T18:00:23Z" level=warning msg="Problem adding backend." backendErr="problem initializing storage driver 'ontap-nas-economy': error initializing ontap-nas-economy driver: could not create Data ONTAP API client: error reading SVM details: Post \"https://<Storage_IP-Address>/servlets/netapp.servlets.admin.XMLrequest_filer\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" handler=Bootstrap newBackendExternal="&{ <UUID> file {0xc0003d05a0 <Storage_mgmt_IP-Address> <Storage_data_IP-Address>  <SVM_Name>         false [] {map[]   {true none none  false ---rwxrwxrwx default unix false ext4 false  {1G}}} [] false    } map[] failed false []}"

 

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device