-
Notifications
You must be signed in to change notification settings - Fork 218
Multiple Start/Stop do not work anymore #1578
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
Comments
What is the use case of multiple start / stop? |
That's what the JUnit extension does before/after each tests. This allow to prepare resources without triggering informer. |
That would mean our tests would fail too, that is not the case, but maybe I'm overlooking something. It not meant to be restarted. But if that helps with some practicalities and does not brings complexity we should fix it, sure. |
I guess JOSDK samples only have one test per project, so the junit extension do not need to stop the operator. |
I think the solution here would be to destroy the informers on stop and re-create them if there's a restart. |
Yep, since informers cannot be restarted atm, this is the only solution |
From quarkiverse/quarkus-operator-sdk#388
I guessed it was a regression introduced with #1358.
I tried to fix it by adding
started = false
at the end ofOperator::stop
but then :With
ConfigurationServiceProvider.overrideCurrent(o -> o.withCloseClientOnStop(false));
With
ConfigurationServiceProvider.overrideCurrent(o -> o.withCloseClientOnStop(true));
The text was updated successfully, but these errors were encountered: