d807f868d6
On the health check prior to rootca update, there was a bug that
prevented CrashLoopBackoff pods being detected as unhealthy. This is
because the pods are in phase "Running", but the status of the
container itself is "ready: false". This commit adds an additional
check to "Running" pods so if any container inside it is not ready,
the pod will be deemed unhealthy.
Test plan:
- PASS: Attempt to perform a rootca update with a pod in
CrashloopBackoff state. Verify the update is not possible
and the health check fails with the pod being show as
unhealthy is "system health-query-kube-upgrade --rootca"
- PASS: Verify the rootca update is possible if no pods are in
CrashloopBackoff state.
Closes-Bug: 2057779
Change-Id: I115b6621df11516db2279fe6bc96452d27975c50
Signed-off-by: Victor Romano <victor.gluzromano@windriver.com>
|
||
|---|---|---|
| .. | ||
| cert-alarm | ||
| cert-mon | ||
| cgts-client | ||
| ipsec-auth | ||
| sysinv | ||
| sysinv-agent | ||