NetApp Failing Pod''s node affinity and Missing routing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Gabriel de Araújo Cabral |
Bug Description
Brief Description
-----------------
1) Routing scripts define at netapp-
2) Trident is failing on pod trident-
NAMESPACE NAME READY STATUS RESTARTS AGE
trident trident-
trident trident-csi-624d7 1/2 Running 0 14m
trident trident-csi-77hhm 1/2 Running 0 14m
trident trident-csi-b8wqj 1/2 Running 0 14m
ansible error:
Warning FailedScheduling 5m10s default-scheduler 0/3 nodes are available: 1 node(s) didn't match Pod's node affinity/selector, 2 node(s) had untolerated taint {node-role.
Severity
--------
Critical: Feature is not usable after the defect
Steps to Reproduce
------------------
kubectl get pods -A Pending status
kubectl describe pod trident-
Expected Behavior
------------------
All the pod is up and running
Actual Behavior
-----------------
As per describe
Reproducibility
---------------
Reproducible
System Configuration
-------
multinode IPV4
Branch/Pull Time/Commit
-------
2022-12-30_18-00-09
Last Pass
---------
N/A
Timestamp/Logs
--------------
N/A
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Gabriel de Araújo Cabral (g-cabral) |
tags: | added: stx.storage |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /ansible- playbooks/ +/871522
Review: https:/