Skip to main content
NetApp Knowledge Base

Trident pods fail to run on OpenShift cluster nodes with specific labels and defaultNodeSelector specified on the scheduler

  1. Last updated
  2. Save as PDF
Views:
67
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Red Hat OpenShift Container Platform (OCP)

Issue

Trident pods fail to run on OpenShift cluster with defaultNodeSelector specified on the scheduler.

Trident pod description shows the warning:

“Warning  FailedScheduling  8m55s  default-scheduler  0/13 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/13 nodes are available: 13 Preemption is not helpful for scheduling.”

 

 

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.