You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sequence of events that is triggering the issue looks as follows:
reconciliation in progress
receiving an event from k8s (and recociliation is skipped) [event 1]
reconciliation finishes and updates the status stanza of the CR
receiving an event from k8s because of the modified status (and it gets skipped) [event 2]
despite the fact that [event 1] hasn't been processed no reconciliation loop is scheduled
following "scheduled reconciliations" (with rescheduleAfter) are ignored too
I do believe that this is a critical bug and we should rise the attention on upgrading in the upcoming release notes.
Thanks @csviri for the support in debugging!
For the records:
As a temporary workaround setting generationAwareEventProcessing = false in the ControllerConfiguration prevent the issue from rising.
I confirm that the upcoming SNAPSHOT release fix the issue 🎉
Thanks!
csviri
changed the title
Concurrency Issue with handling the updated resource after reconciliation.
Race Condition with handling the updated resource after reconciliation.
Mar 15, 2022
Uh oh!
There was an error while loading. Please reload this page.
(This part was reworked for 2.2.0 / 3.0.0 already, that is not effected)
The text was updated successfully, but these errors were encountered: