跳转到主内容

用户无法通过证书验证访问S3存储分段

Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2010015104</a>
Last Updated:

适用场景

  • ONTAP
  • ONTAP S3存储分段

问题描述

  • 访问S3存储分段时收到以下错误:
Could not connect to storage default. Error:get "https://s3store.abc.xyz/openshiftint...try/?location=": tls: failed to verify certificate: x509: certificate signed by unknown authority
  • 此外、
Error: Certificate is not valid
  • 从事件日志中、我们可以看到TLS连接因证书错误而失败

     Mon Jul 29 12:59:19 +0530 [Node-01: ktlsd: ktls.failed:notice]: "The TLS connections have failed several times with remote host '172.17.204.40' in IPspace '4294967295', for which the latest reason given is: OpenSSL: error:0A000412:SSL routines::sslv3 alert bad certificate."
     

  • 在消息部分中、握手失败、并显示证书错误
     
    Mon Jul 29 2024 12:59:19 +05:30 [Jul 29 12:59:19]: ERR: ktlsd: abortHandshake:src/tables/net_ssl_handshake.cc:2073 OpenSSL call failed: OpenSSL: error:0A000412:SSL routines::sslv3 alert bad certificate
    Mon Jul 29 2024 13:01:55 +05:30 [Jul 29 13:01:55]: ERR: security_shared::filesystem::ScopedFlock: [createDirectoriesAndOpenFile]:166: Failed to create directories: Invalid argument
    Mon Jul 29 2024 13:01:55 +05:30 [Jul 29 13:01:55]: ERR: libsslmgnt::filesystem::AbstractPemBundle: [getData]:42: Unable to acquire lock in

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.