Sync gets stuck on error despite newer commit existing - configurable timeout, or improved algorithm

[erikschul]

Summary

Sometimes a bad yaml is pushed, and ArgoCD encounters and error during syncing. A fix is pushed, but ArgoCD doesn't abort the current sync, which is stuck.

Possibly related to: #6208

Motivation

It seems to automatically abort/retry after about 5-10 minutes, but that's too long.

Proposal

Perhaps the algorithm needs to abort and retry if a newer commit is available?
Or there should be a configurable timeout where it aborts if no progress is made within 60s.

[aslafy-z]

I believe this is a duplicate of #11494

[crenshaw-dev]

Let's close this in favor of the other, unless @erikschul has a reason to split the conversation.