Readiness check for some services returns 500 status code

[PrajwolAmatya]

related #8783 #10316

Description

Checking the readiness of some services returns 500 status code:

• graph
• idp
• proxy

curl -kv http://localhost:9124/readyz

Response:

< HTTP/1.1 500 Internal Server Error
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate, value
< Content-Type: text/plain
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Last-Modified: Tue, 26 Nov 2024 11:07:30 GMT
< Vary: Origin
< X-Graph-Version: 7.0.0-rc.2+9a7c8a43f8
< Date: Tue, 26 Nov 2024 11:07:30 GMT
< Content-Length: 21
< 
* Connection #0 to host localhost left intact
Internal Server Error% 

Likewise check for the service auth-bearer do not work.

curl -kv http://localhost:9149/readyz

Response:

*   Trying 127.0.0.1:9149...
* connect to 127.0.0.1 port 9149 failed: Connection refused
*   Trying ::1:9149...
* connect to ::1 port 9149 failed: Connection refused
* Failed to connect to localhost port 9149 after 0 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to localhost port 9149 after 0 ms: Connection refused

[PrajwolAmatya]

All service check now returns the correct status code 200. Covered in PR #10351. So, closing this issue.

[amrita-shrestha]

This issue is valid and is being reopened. The problem lies in the test code, which is sending requests to the following incorrect URL: https://localhost:9200/ocalhost:9229/healthz and https://localhost:9200/ocalhost:9229/readyz

As a result, the server returns a 200 status code, but the request is not directed to the intended endpoint, causing tests to pass erroneously.