Skip to main content
NetApp Knowledge Base

Application pods fail to schedule on new node after an abrupt node shutdown/reboot

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

Applies to

  • Astra Trident
  • OpenShift Container Platform
  • Ericsson Cloud Container Distribution
  • Kubernetes

Issue

Application pods fail to schedule on new node after an abrupt node shutdown/reboot.

•   Master node n2 is offline

@control-plane-mast-n1:~> kubectl get no
NAME                          STATUS     ROLES           AGE     VERSION
control-plane-mast-n1   Ready      control-plane   7h58m   v1.32.2
control-plane-mast-n2   NotReady   control-plane   7h38m   v1.32.2
control-plane-mast-n3   Ready      control-plane   7h24m   v1.32.2
pool1-wk1-n4        Ready      worker          6h55m   v1.32.2
 

•   New pod is scheduled on master node n3
 
@control-plane-mast-n1:~> kubectl get po -Ao wide | grep reg
kube-system        registry-69ddbbbd77-bk4jz             0/2     ContainerCreating   0               9m45s   <none>            control-plane-mast-n3   <none>           <none>

•   Volume attachment is still there on the old node
 
@control-plane-mast-n1:~> kubectl get volumeattachments.storage.k8s.io | grep pvc-d7281344-346e-4bec-a8e8-3dcb933458f8
csi-aeabd505e10f39a031c7187bc0bf7be60664b23bfa41c949b4f80eecedd91bcb   csi.trident.netapp.io   pvc-d7281344-346e-4bec-a8e8-3dcb933458f8   control-plane-dc286-mast-n2   true       6h29m
 

 

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.