Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health checks related to the Discovery Service ignores authentication service state #1549

Closed
balhar-jakub opened this issue Jun 17, 2021 · 0 comments
Labels
bug Verified defect in functionality good first issue Good for newcomers Priority: Medium

Comments

@balhar-jakub
Copy link
Member

Describe the bug
The discovery service-protected endpoints access depends on the accessibility of the Authentication service. The health of the service doesn't reflect this fact though, as such the composite health endpoint on Gateway also doesn't take this fact into account.

Steps to Reproduce

  1. Start all the services
  2. Kill gateway service
  3. Access authenticated endpoint e.g. /discovery/api/v1/staticApi
  4. 503 is returned
  5. /application/health on discovery service returns just that the service is up.

Expected behavior
/application/health on discovery service and gateway service should at least somehow keep the information that the service isn't fully operational.

@balhar-jakub balhar-jakub added bug Verified defect in functionality new New issue that has not been worked on yet labels Jun 17, 2021
@anton-brezina anton-brezina added Priority: Medium good first issue Good for newcomers and removed new New issue that has not been worked on yet labels Jun 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Verified defect in functionality good first issue Good for newcomers Priority: Medium
Projects
None yet
Development

No branches or pull requests

3 participants