Too many reconciliation errors/warnings for machine deployment objects

[akash-gautam]

When we create or update machine deployments there are many errors/warnings saying operations can't be fulfilled because the object has been modified, which I think happens due to resource version changes when concurrent updates happen to the machine deployment object. A support request was raised mentioning that we should try to improve this as this can confuse the admins on whether deployment is successful or not or if they made any error on their part.

Warning ReconcileError 2m9s (x3 over 2m9s) machinedeployment-controller Operation cannot be fulfilled on machinedeployments.cluster.k8s.io "kkp-tst-root-pool1": the object has been modified; please apply your changes to the latest version and try again

"The error message doesn't necessitate a failure, however it is the same message whether the deployment succeeds or fails, which makes it difficult to monitor, causing me to manually check up on any all deployments. I would say it is very much a low priority, more a quality of life issue."

More details on #INC-6541

[kubermatic-bot]

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale