跳转到主内容

三元更新后端失败- 400个错误请求

Views:
9
Visibility:
Public
Votes:
0
Category:
trident-kubernetes<a>2009878759</a>
Specialty:
snapx
Last Updated:

适用场景

Astra三端

问题描述

由于无法挂载卷、因此、三端存储设备后端脱机导致Pod创建失败:
 
time="2021-04-20T18:24:28Z" level=error msg="GRPC error: rpc error: code = Internal desc = backend xxx.xxx.xxx is not Online or Deleting"
 
 
# tridentctl get backend -n trident
+---------------------+----------------+--------------------------------------+--------+---------+
|     NAME     | STORAGE DRIVER |         UUID         | STATE  | VOLUMES |
+---------------------+----------------+--------------------------------------+--------+---------+
| BACKEND_NAME     | ontap-nas    | 586b1cd5-8cf8-428d-a76c-2872713612c1 | failed |    52 |
+---------------------+----------------+--------------------------------------+--------+---------+
 
 
[user@hostname]$./tridentctl update backend <BACKEND_NAME> -n trident -f <BACKEND.json> -d operating mode - tunnel, Trident pod - trident-controller-6695f7657-tb629, Namespace - trident, CLI - kubectl
invoking tunneled command: kubectl exec trident-controller-6695fd7657-tb629 -n trident -c trident-main -- tridentctl --debug update backend --base64 eyJiYWN:2W5kImFtZSI6ImVpbTEiLCJkYXRhTE1G joiMTAuM}EyLjIWNC4xNTQiLCJk2WZhdWx0cyI6eyJleHBvenRQb2xpY3ki01Jk2W2hdWx0Iiwic25hcHNob3RQb2xpY3kiOiJub251IiwidW5peFB1cm1pc3Npb25zIjoiDc3NyJ9LCJtYW5h22V+2W50TEIGIjoiMTAuM}EyLjIwNC4×NTUILCJwY
zaW9uIjoxfQ== BACKEND_NAME
Operating mode - direct, Server - 127.0.0.1:8000, Autosuport server - 127.0.0.1:8003
--------------------------------------------------------------------------------
Request Method: POST
Request headers: map [Content-Type: [application/json]]
Request body: {"backendName": "<BACKEND_NAME>", "dataLIF": "<DATA_LIF_IP>", "defaults": ("exportPolicy": "default", "snapshotPolicy": "none", "unixPermissions": "0777"), "managementLIF": "<MGMT_LIF_IP>", "раssword": "<PASSWORD>", "storageDriverName": "ontap-nas", "storagePrefix": "<BACKEND_NAME>", "svm": "<STORAGE_CONTROLLER_NAME>", "username"; "<USER_NAME>", "version": 1)
...............................................................................
Error: could not update backend BACKEND_NAME: problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error creating ONTAP API
client: error reading SVM details: API status: failed, Reason: The proxy server failed to communicate with the ontapi server at address 127.0.0.1, Code: 13114 (400 Bad Request)
Response status: 400 Bad Request
Response headers: map[Content-Length: [334] Content-Type: [application/json; charset-UTF-8] Date: [Wed, 13 Dec 2023 13:47:01 GMT]] 
Response body: {"backend":"", "error":"problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error creating ONTAP API
Client: error reading SVM details: API status: failed, Reason: The proxy server failed to communicate with the ontapi server at address 127.0.0.1, Code: 13114"}
command terminated with exit code 1

 

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.