CrashLoopBackoff pods not being detected by kube rootca health check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Victor Romano |
Bug Description
Brief Description
-----------------
Kube rootca update continue to run if there's a pod in CrashLoopBackoff state.
Severity
--------
Minor
Steps to Reproduce
------------------
1. sw-manager kube-rootca-
2. sw-manager kube-rootca-
Expected Behavior
------------------
Apply should fail because of failed pod
Actual Behavior
----------------
Apply continue
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any system (tested on a duplex system)
Branch/Pull Time/Commit
-------
NA
Last Pass
---------
NA
Timestamp/Logs
--------------
NA
Test Activity
-------------
Developer testing
Workaround
----------
NA
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.10.0 stx.config |
Changed in starlingx: | |
assignee: | nobody → Victor Romano (vgluzrom) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /config/ +/912770
Review: https:/