Skip to main content
NetApp Knowledge Base

Failed to spin up prometheus pod with the error "secret not found"

  1. Last updated
  2. Save as PDF
Views:
54
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident
  • OpenShift Container Platform (OCP)
  • Prometheus pod

Issue

Failed to spin up prometheus pod with the following error.

Kubelet log from the node where prometheus pod is scheduled.

rhel1.demo.netapp.com hyperkube[3165]: E0318 12:01:29.244462    3165 nestedpendingoperations.go:348] Operation for "{volumeName:kubernetes.io/secret/8b48489a-6b79-40d3-87fb-3746d9a2ea00-secret-grpc-tls podName:8b48489a-6b79-40d3-87fb-3746d9a2ea00 nodeName:}" failed. No retries permitted until 2024-03-18 12:01:45.244418081 +0000 UTC m=+2752993.551728987 (durationBeforeRetry 16s). Error: MountVolume.SetUp failed for volume "secret-grpc-tls" (UniqueName: "kubernetes.io/secret/8b48489a-6b79-40d3-87fb-3746d9a2ea00-secret-grpc-tls") pod "prometheus-k8s-1" (UID: "8b48489a-6b79-40d3-87fb-3746d9a2ea00") : secret "prometheus-k8s-grpc-tls-15d7fd5vj1e57" not found

 

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.