メインコンテンツまでスキップ

ONTAP-113520:Cloud KMSの「reachable」ステータスがtrueになるが、「message」と「code」はエラーを示している

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

問題

When checking Cloud KMS (Key Management Service) reachability via the ONTAP REST API, the global reachability status incorrectly shows as reachable but the message field indicates that a subset of nodes are unable to reach the service and the code field has a non-zero value. This could happen when checking the reachability immediately after enabling a Cloud KMS feature (ex. AKV KMS, GCP KMS, AWS KMS). Example REST output with issue: "azure_reachability": {

"reachable": true, "message": "Azure Key Vault unreachable from the following nodes: Node: OntapNode0. Reason: Azure Key Vault (AKV) operation \"GET\" failed.\nCryptsoft error: IO\nCryptsoft status: SUCCESS\nCryptsoft reason: SUCCESS\nCryptsoft message: \nHTTP response code: \nHTTP payload: \n\nUnable to communicate with the AKV instance.\nIssue (privilege: diag) \"security key-manager external <azure|aws|gcp|ikp> invoke\" for more information. ", "code": "65537549"

} As an example, if all nodes are actually able to reach an AKV instance, the REST output will look like the following: "azure_reachability": {

"reachable": true, "message": "", "code": "0"

}

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.