rinaldodev opened a new issue, #3761: URL: https://github.com/apache/camel-k/issues/3761
Recently there has been a change to grab the error message for the Ready condition, when False, from camel's health check: https://github.com/apache/camel-k/blob/151def156ef0bcb8f4b05e95a2eb7de75cf111fd/pkg/controller/integration/monitor.go#L437-L445 This does work from time to time, but in some cases it doesn't. By talking to @astefanutti it seems to be related to this check: https://github.com/apache/camel-k/blob/151def156ef0bcb8f4b05e95a2eb7de75cf111fd/pkg/controller/integration/monitor.go#L269-L271 Since the above check if the deployment progressing condition is false, and returns early, it doesn't get to the point of probing the pod's health check in the next few lines of code. Here is an example where a pod is not ready, but could still be probed: ``` mctr-cd78npqi585nmcobr0bg-69bc58cbff-6g95b 0/1 Running 0 16m ``` ``` { "status": "DOWN", "checks": [{ "name": "custom-camel-routecontroller-health-check", "status": "DOWN", "data": { "route.id": "cd78npqi585nmcobr0bg-source", "error.message": "Not authorized to access group: cd78npqi585nmcobr0bg", "route.status": "stopped", "check.kind": "READINESS" } }, { "name": "context", "status": "UP", "data": { "context.name": "camel-1", "context.version": "3.18.2", "context.status": "Started", "check.kind": "READINESS" } }] } ``` Because of this behavior, the Ready condition ends up containing the following message: ``` message: ReplicaSet "mctr-cd78npqi585nmcobr0bg-69bc58cbff" has timed out progressing. ``` while not informing the real root cause that is present in the health check: `Not authorized to access group: cd78npqi585nmcobr0bg` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
