Fix annoying optimistic locking error in logs #578
Description
Every first new user see that and thinks that something is wrong, but error is harmless. We either should stop logging it or somehow change approach to update the objects to not get optimistic locking error.
ersion and try again"}
github.com/ytsaurus/ytsaurus-k8s-operator/pkg/apiproxy.(*Ytsaurus).SaveClusterState
/workspace/pkg/apiproxy/ytsaurus.go:112
github.com/ytsaurus/ytsaurus-k8s-operator/controllers.(*YtsaurusReconciler).Sync
/workspace/controllers/sync.go:194
github.com/ytsaurus/ytsaurus-k8s-operator/controllers.(*YtsaurusReconciler).Reconcile
/workspace/controllers/ytsaurus_controller.go:70
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Reconcile
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:116
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:303
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:263
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2
/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:224
2025-10-23T00:03:54.564Z INFO Warning: Reconciler returned both a non-zero result and a non-nil error. The result will always be ignored if the error is non-nil and the non-nil error causes reqeueuing with exponential backoff. For more
details, see: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/reconcile#Reconciler