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

Probes failure results in RH-SSO pod crash #1006

Closed
iam-veeramalla opened this issue Sep 26, 2023 · 0 comments · Fixed by #1007 or #1008
Closed

Probes failure results in RH-SSO pod crash #1006

iam-veeramalla opened this issue Sep 26, 2023 · 0 comments · Fixed by #1007 or #1008
Assignees
Labels
bug Something isn't working

Comments

@iam-veeramalla
Copy link
Collaborator

Describe the bug
The latest version of RH-SSO (rh-sso-76) pod crashes intermittently due to the liveness and readiness probes failure.

Readiness probe failed: {
    "probe.eap.dmr.EapProbe": "Error sending probe request: Expecting value: line 1 column 1 (char 0)",
    "probe.eap.dmr.HealthCheckProbe": "Error sending probe request: Expecting value: line 1 column 1 (char 0)"
}
INFO Using the 'FSydNEtvOaSJCPTKgQVfqRCMaAyVbqmZ' username to authenticate the probe request against the JBoss DMR API.
INFO Using the 'FSydNEtvOaSJCPTKgQVfqRCMaAyVbqmZ' username to authenticate the probe request against the JBoss DMR API.
Liveness probe failed: {
    "probe.eap.dmr.EapProbe": "Error sending probe request: Expecting value: line 1 column 1 (char 0)",
    "probe.eap.dmr.HealthCheckProbe": "Error sending probe request: Expecting value: line 1 column 1 (char 0)"
}
INFO Using the 'FSydNEtvOaSJCPTKgQVfqRCMaAyVbqmZ' username to authenticate the probe request against the JBoss DMR API.
INFO Using the 'FSydNEtvOaSJCPTKgQVfqRCMaAyVbqmZ' username to authenticate the probe request against the JBoss DMR API.

To Reproduce
Steps to reproduce the behavior:

  1. Enable keycloak as sso using .spec.sso.provider: keycloak in the Argo CD CR.
  2. Wait for the keycloak pod to crash.

Expected behavior
Keycloak pod is up and running.

Screenshots
Error message provided above.

Additional context
This can probably be fixed by increasing the initialdelayseconds and timeoutseconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant