You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on timing, one of two things will happen. If the wait starts waiting on an app that is that is being deleted, it will start waiting- the app gets fully removed - and it will timeout waiting. Or... the app gets deleted before it starts waiting on it, and it throws an error saying some-app not found.
To Reproduce
Create an app of apps with child apps (we have 25 or so)
Sync so they are all in the cluster and working
Remove a child app from the bootstrap app
Run sync. You will see the app start to get pruned. The sync will exit.
As the app is being removed...run wait with a selector that selects all the child apps
You should see the behavior mentioned here.
Expected behavior
I would expect argocd app wait -l some-label=some-value not to select apps that are being deleted.
Describe the bug
When using a label selector with
argocd app wait
, it seem to select apps that are also in the process of being deleted.Depending on timing, one of two things will happen. If the wait starts waiting on an app that is that is being deleted, it will start waiting- the app gets fully removed - and it will timeout waiting. Or... the app gets deleted before it starts waiting on it, and it throws an error saying
some-app not found
.To Reproduce
Expected behavior
I would expect
argocd app wait -l some-label=some-value
not to select apps that are being deleted.Version
The text was updated successfully, but these errors were encountered: