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
Describe the bug
After ci-cd the revision on the application points toward a not-existing yet branch.
When the new branch is created, the application is still stuck on earlier error message and only after a manual refresh the application returns to a green state.
This problem happens occasionally, and according to logs I do see most of the times in the argocd server that a webhook did arrive.
I managed to reproduce the problem only on bitbucket.
To Reproduce
create argocd application.
change argocd application to point toward a non existent branch
create the new branch
Expected behavior
After the new branch is created the application automatically refreshes itself.
Version
argocd version: 2.11.4
ocp version: 4-10
The text was updated successfully, but these errors were encountered:
There are refreshes every 3 min by default. Are they helpful? I think Argo doesn't know a way to know about branch now being available unless you set up webhooks https://argo-cd.readthedocs.io/en/stable/operator-manual/webhook/. Please, let me know more details about what's happening and whether these points help.
Describe the bug
After ci-cd the revision on the application points toward a not-existing yet branch.
When the new branch is created, the application is still stuck on earlier error message and only after a manual refresh the application returns to a green state.
This problem happens occasionally, and according to logs I do see most of the times in the argocd server that a webhook did arrive.
I managed to reproduce the problem only on bitbucket.
To Reproduce
Expected behavior
After the new branch is created the application automatically refreshes itself.
Version
argocd version: 2.11.4
ocp version: 4-10
The text was updated successfully, but these errors were encountered: