-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
None
Description of problem:
When 40_microshift_running_check.sh fails, it doesn't say where the problem was specifically: it prints out that all namespaces are checked for pod restart, but when some fails it just prints FAILURE without any context
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
script output Checking pod restart count in the 'openshift-ovn-kubernetes' namespace Checking pod restart count in the 'openshift-service-ca' namespace Checking pod restart count in the 'openshift-ingress' namespace Checking pod restart count in the 'openshift-dns' namespace Checking pod restart count in the 'openshift-storage' namespace FAILURE
Expected results:
Script prints information about which namespace/pod failed and why (what condition was unfulfilled, like ratio between samples with and without restarts). Maybe time needed for this check can be extended since it's running in parallel now
Additional info:
- relates to
-
USHIFT-1389 greenboot healthcheck script reports what it checks but not why it fails
- Closed
- links to