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
ClusterLogForwarder's status is constantly replaced, leading to infinite reconciliation runs #2315
Comments
/assign |
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 9, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 9, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 19, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 19, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 19, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 19, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
andreaskaris
added a commit
to andreaskaris/cluster-logging-operator
that referenced
this issue
Feb 19, 2024
Test for openshift#2315 Signed-off-by: Andreas Karis <ak.karis@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ClusterLogForwarder's status is constantly replaced, leading to infinite reconciliation runs
The following code:
always repalces the entire CLF status. That in turn leads to constant status updates of the type Ready condition where lastTransitionTime is always set, even though no actual transition happens.
In turn, the operator infinitely reconciles resources, even though nothing happens.
You can easily see this by running the current version of the Operator with debug level 3:
With the following 2 resources in place:
The text was updated successfully, but these errors were encountered: