You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lewisdaly opened this issue
Feb 9, 2021
· 1 comment
Assignees
Labels
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceoss-coreThis is an issue - story or epic related to a feature on a Mojaloop core service or related to it
Thanks for quickly fixing this @shashi165 ; I think its worth ensuring this behavior on other core services as well (quoting service, central ledger, settlement services, as well)
bugSomething isn't working or it has wrong behavior on a Mojaloop Core serviceoss-coreThis is an issue - story or epic related to a feature on a Mojaloop core service or related to it
Summary:
On the ALS, GET /health returns a 200 OK when status is DOWN.
This is an issue because K8s won't try and recreate the pod since it uses the status code to determine the health of pods
Severity:
(Low, Medium, High)
Priority:
(Critical, Medium, Low)
Expected Behavior
Steps to Reproduce
Observe that the response is
200 OK
, even though there is no database connected.Specifications
PR:
Notes:
The text was updated successfully, but these errors were encountered: