-
Notifications
You must be signed in to change notification settings - Fork 35
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
HttpAdvancedIT fails with Keyclaok container insufficient memory error in Podman Jenkins jobs #2106
Comments
|
Summary of Investigations:
Executed in our Podman-based Jenkins job.
|
What about " memoryLimitMiB = 768?" What |
Output in Jenkins:
Output in Jenkins:
and test passed OK |
only the last one or both cases? |
Only the last one, with |
Both are using similar memory, so what's the difference? |
@mabartos do you have any idea why the |
That's all interesting, but as far as actual failure goes, this sentence from the issue description is what matters most:
Here is what you need to do: implement |
There are two things:
After my experiments on my local machine, the container limit was always set and I haven't spotted any issue with that. Wondering why it behaves differently in Jenkins. As values @jcarranzan Until this issue is resolved, and your workaround sets these values, it'd be good to change the |
It's just failing in Podman Jenkins jobs and HttpAdvancedIT, but we use the same Keycloak service container for other tests in http-module.
Some points about my previous investigation:
The issue occurs before tests start. The failure is nor related to the HttpAdvancedIT tests. When Keycloak container tries to allocate memory ,ther's already insufficient memory due to a resource leak.
I've observed differences between Jenkins executors, Docker is 16Gb vs Podman 8 Gb, this could explains why the tests pass on Docker but fail in Podman jobs.
There was Keycloak memory adjustment in our TF with this PR(Set memory limit for Keycloak container quarkus-test-framework#1351) to limit memory usage to 1GB but did not resolve this issue on Podman jobs.
I applied a workaround in my PR(Fix not enough space error for keycloak container image quay.io/keycloak/keycloak:25.0 #2067 ) by adding :
.withProperty("JAVA_OPTS", "-Xms512m -Xmx1g")
and the test passed.The text was updated successfully, but these errors were encountered: