-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
RejectedExecutionException when checking status of removed operator through BaseOperation.get #4491
Comments
This means that the client/httpclient has been closed - we probably need a higher level check for that to make it clear. Can you find in your code where the client is being closed early? |
We closing the client twice, once as a part of Junit cleaning after all tests and once as a part of Junit cleaning on closing. But we have this problem only with strimzi operator and not, for example, with strimzi deployed in a separate container(test |
This is unrelated to the functional part of the test, it's just related to when it's being closed - this operation is being performed after it's closed. Can you put a breakpoint on the client close to see where it is happening early? |
Yes, we call That surprises me, that the same process works flawlessly with non-operator workload. |
Describe the bug
I have a code, which uses kubernetes client to deploy OpenShift operator and application and to check its status. After deleting a project and doing a final check, what everything was deleted properly, I receive a cryptic exception:
java.util.concurrent.RejectedExecutionException: Task okhttp3.RealCall$AsyncCall@553d2579 rejected from java.util.concurrent.ThreadPoolExecutor@2a8f6e6[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 166]
. The very same code forked flawlessly with the 5 version of Kubernetes clientFabric8 Kubernetes Client version
6.1.1
Steps to reproduce
git clone git@github.com:fedinskiy/quarkus-test-framework.git -b reproducer/fabric8
cd quarkus-test-framework
mvn clean install -DskipTests -DskipITs
mvn clean verify -Popenshift -Pexamples -pl examples/kafka -Dquarkus.platform.version=999-SNAPSHOT
with 6.1.1mvn clean verify -Popenshift -Pexamples -pl examples/kafka
Expected behavior
BaseOperation.get should either return custom resource with proper status or null for non-existing resources or throw an error, which is easy to understand.
Runtime
OpenShift
Kubernetes API Server version
1.24.2@latest
Environment
Linux
Fabric8 Kubernetes Client Logs
Additional context
Related issues:
quarkusio/quarkus#28405 — client libraries are provided by Quarkus, but Quarkus team do not change them
#4448 — similar bug, but caused by usage of try-with resources.
The text was updated successfully, but these errors were encountered: