Describe the bug
When synchronization fails due to attempting to change readonly fields in certain resources, or if there is an error in the specifications, the application gets stuck in the Synchronization state with a pending deletion status in BeforeHookCreation jobs. It can remain in this state for days until someone manually terminates it
The application should be properly synced with these specifications.
In the next step, try to make a change in the StatefulSet, such as adjusting the size of the volume claim. After doing so, the application will become stuck in a synchronization state indefinitely.
Checklist:
argocd version
.Describe the bug When synchronization fails due to attempting to change readonly fields in certain resources, or if there is an error in the specifications, the application gets stuck in the Synchronization state with a pending deletion status in BeforeHookCreation jobs. It can remain in this state for days until someone manually terminates it
To Reproduce
Deploy application with following specs
kustomization.yaml
main.yaml
application.yaml
The application should be properly synced with these specifications.
In the next step, try to make a change in the StatefulSet, such as adjusting the size of the volume claim. After doing so, the application will become stuck in a synchronization state indefinitely.
repository with above specs: https://github.com/sklgromek/argo-sync-fail
Expected behavior
Sync process should be stopped when failed, without trying to run hooks
Screenshots
Version
But I notice the same also on version
Logs