Random race condition in the restore with managed fields #8132
Assignees
Labels
Comments
mpryc
added a commit
to mpryc/velero
that referenced
this issue
Aug 20, 2024
This commit addresses issue vmware-tanzu#8132, where an error randomly appears in the logs during the restore operation. The error occurs due to a race condition when attempting to patch managed fields on an object that has been modified in the cluster. The error message indicates that the operation cannot be fulfilled because the object has been modified, suggesting that changes should be applied to the latest version. To resolve this, a retry mechanism has been implemented in the restore process when encountering this error, ensuring that managed fields are properly restored without the error message appearing in the logs. Signed-off-by: Michal Pryc <[email protected]>
3 tasks
mpryc
added a commit
to mpryc/velero
that referenced
this issue
Aug 21, 2024
This commit addresses issue vmware-tanzu#8132, where an error randomly appears in the logs during the restore operation. The error occurs due to a race condition when attempting to patch managed fields on an object that has been modified in the cluster. The error message indicates that the operation cannot be fulfilled because the object has been modified, suggesting that changes should be applied to the latest version. To resolve this, a retry mechanism has been implemented in the restore process when encountering this error, ensuring that managed fields are properly restored without the error message appearing in the logs. Signed-off-by: Michal Pryc <[email protected]>
mpryc
added a commit
to mpryc/velero
that referenced
this issue
Aug 21, 2024
This commit addresses issue vmware-tanzu#8132, where an error randomly appears in the logs during the restore operation. The error occurs due to a race condition when attempting to patch managed fields on an object that has been modified in the cluster. The error message indicates that the operation cannot be fulfilled because the object has been modified, suggesting that changes should be applied to the latest version. To resolve this, a retry mechanism has been implemented in the restore process when encountering this error, ensuring that managed fields are properly restored without the error message appearing in the logs. Signed-off-by: Michal Pryc <[email protected]>
Could you check what the resource is represented by the name |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
There is a race condition in the restore operation causing random errors visible in the logs during restore operation. Below is stripped down log presenting the error during restore:
What did you expect to happen:
Managed fields properly restored without error message in the logs.
The text was updated successfully, but these errors were encountered: