-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.13
-
None
-
Moderate
-
None
-
5
-
Sprint 229, Sprint 230, Sprint 231, Sprint 232, Sprint 233, Sprint 234, Sprint 236, Sprint 237, Sprint 238, Sprint 239, Sprint 240, Sprint 249, Sprint 250
-
13
-
Rejected
-
False
-
Description of problem:
CanaryChecksRepetitiveFailures: Canary route checks for the default ingress controller are failing
doesn't give much detail or suggest next-steps. Expanding it to include at least a more detailed error message would make it easier for the admin to figure out how to resolve the issue.
Version-Release number of selected component (if applicable):
It's in the dev branch, and probably dates back to whenever the canary system was added.
How reproducible:
100%
Steps to Reproduce:
1. Break ingress. FIXME: Maybe by deleting the cloud load balancer, or dropping a firewall in the way, or something.
2. See the canary pods start failing.
3. Ingress operator sets CanaryChecksRepetitiveFailures with a message.
Actual results:
Canary route checks for the default ingress controller are failing
Expected results:
Canary route checks for the default ingress controller are failing: ${ERROR_MESSAGE}. ${POSSIBLY_ALSO_MORE_TROUBLESHOOTING_IDEAS?}
Additional info:
Plumbing the error message through might be as straightforward as passing probeRouteEndpoint's err through to setCanaryFailingStatusCondition for formatting. Or maybe it's more complicated than that?
- causes
-
OCPBUGS-37491 co/ingress status cannot reflect the real condition
- Verified
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update