User story (meta) #2222
PT distributePolicy: Check status of webapp and endpoint, and restart jetty if several continuous tests fail
|Assignee:||Matthieu CERDA||% Done:||
|Target version:||Rudder - 2.4.0~alpha5||Estimated time:||2.00 hours|
Initially we can just run a curl check on a simple URL, and ensure we get a HTTP 200 OK response code.
Later, we can extend this to use the built-in REST API and call something like /api/status which should return a text string "OK".
#1 Updated by Matthieu CERDA about 3 years ago
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 8ec83355feab16b7850fb5636e58016d28e1dbc9.
#2 Updated by Matthieu CERDA about 3 years ago
- Status changed from Pending technical review to Discussion
This commit implements the check only for the webapp. Indeed, the inventory endpoint only responds to POST methods and a GET returns a 405 error (Method not supported). I do not think that trying to post something at every run is a good idea, so it is for me a better idea to wait for the enhanced version that will use the REST API to check the status. Also, there were some discussions about merging the webapp and the endpoint !
#3 Updated by Jonathan CLARKE about 3 years ago
Just one question: I don't see any "result_repaired" reports for when we restart jetty. Do they come from the bundle that is called, or have they been forgotten?
#4 Updated by Matthieu CERDA about 3 years ago
They come from the called bundle indeed. Nothing forgotten :)
#5 Updated by François ARMAND about 3 years ago
- Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
#6 Updated by Matthieu CERDA about 3 years ago
- Status changed from Discussion to Pending technical review
Every step completed in the commit b6a0156e0523187a3fd8e60b6f975bffd5991860
#7 Updated by Jonathan CLARKE about 3 years ago
- Status changed from Pending technical review to Pending functional review
Looks good to me!