Skip to main content
NetApp Knowledge Base

COTV-8101: ONTAP Tools 10: Deployment fails as the ntv-vault-transit pod is unable to start

  1. Last updated
  2. Save as PDF
Views:
2
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
VIRT
Last Updated:

Issue

During the deployment of ONTAP Tools for VMware vSphere 10, the ntv-vault-transit enters into a CrashLoopBackoff state. 
When reviewing recent events for the OTV kubernetes cluster raised during the failed deployment, the following failing readiness check is seen:
$ kubectl get events -n ntv-system --sort-by='.lastTimestamp'
52s         Warning   Unhealthy                pod/ntv-vault-transit-12345678-abcd           Readiness probe failed: Error checking seal status: Get "https://ntv-vault-transit-internal.ntv-system.svc.cluster.local:8200/v1/sys/seal-status": dial tcp 192.168.0.50:8200: connect: connection refused
The "connection refused" warning references a IP address that is external to the ONTAP Tools appliance.

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.