Possible race during operator restart causes seemingly benign error log

[judgeaxl]

Each time my operator instance is restarting, I see the following error log:

error patching conditions: The condition "Ready" was modified by a different process and this caused a merge/ChangeCondition conflict:   &v1.Condition{
  	... // 3 identical fields
  	LastTransitionTime: {Time: s"2025-01-23 12:23:48 +0000 UTC"},
  	Reason:             "Succeeded",
- 	Message:            "Reporting finished in 162ms",
+ 	Message:            "Reporting finished in 161ms",
  }

As far as I can tell this happens for any expected restart, e.g. kubectl rollout restart deploy/flux-operator or Helm chart upgrade.

I've not been able to find any problems other than the error log, and the situation does seem to resolve itself right after. So presumably this could be followed up with another entry claiming all is well once it is, or be degraded to a warning, unless it repeatedly fails. Just to calm users' minds.

The operator was deployed on AWS EKS using Helm. A FluxInstance resources was deployed using kubectl. Both were then taken over by appropriate resources in the backing GitRepository source.

Operator Version: v0.13.0
FluxCD Version: v2.4.0