Skip to main content
NetApp Knowledge Base

The ktls.failed:notice is detected when CVO been takeover due to Azure maintenance

  1. Last updated
  2. Save as PDF
Views:
314
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
microsoft_azure
Last Updated:

Applies to

NetApp Cloud Volume ONTAP(CVO)

Issue

  • The below issue happens when the CVO node been takeover due to Azure side maintenance or unexpected reboot.
    • NetApp Console:
      Degraded - Show Details
      HA cluster is not highly available.The node giveback was not completed.
    • EMS Log:
       [<NODE>: ktls.failed:notice]: "The TLS connections have failed several times with remote host 'xx.xx.xx.xx' in IPspace 'xxxxxx', for which the latest reason given is: OpenSSL: error:0A000086:SSL routines::certificate verify failed."
       [<NODE>: ktls.failed:notice]: "The TLS connections have failed several times with remote host 'xx.xx.xx.xx' in IPspace 'xxxxxx', for which the latest reason given is: Errno: Connection reset by peer."
       [<NODE>: ktls.failed:notice]: "The TLS connections have failed several times with remote host 'xx.xx.xx.xx' in IPspace 'xxxxxx', for which the latest reason given is: TLS: Handshake timed out."
       [<NODE>: ktls.failed:notice]: "The TLS connections have failed several times with remote host 'xx.xx.xx.xx' in IPspace 'xxxxxx', for which the latest reason given is: SMF: internal network error."
  • If Azure maintenance window is 2 days, EMS Log also reports error:
object.store.unavailable: Unable to connect to the object store "StorageAccount" from node <NODE-ID>. Reason: Connection unavailable.

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.