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
Related to #18120 case, after upgrade to Argocd Chart 6.9.1 (app 2.11.0) from 6.7.18 (app 2.10.9) the error "resolv repo version" is shown during a manual sync. After apply a downgrade to 6.7.18 it works properly. The same problem with 6.8.x (also app 2.11.0) Chart version.
To Reproduce
When a manual sync starts the error is shown in a pop-up.
Expected behavior
It should starts to sync all components, if any of them has changes to apply. It only works when at least chart version 6.7.18 (app 2.10.9) is deployed.
Screenshots
Version
Versions affected 6.8.x and 6.9.x:
Last version without this problem:
Logs
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
I suspect we need to wait for the chart to be updated to use a new release as the current 2.11.0 is a week old and carries this bug. Folks are reporting this is fixed in Master.
Is downgrading an option to work around this in the mean time? I would assume just changing the repo-server image would be enough.
Assumption incorrect, just changing the repo-server gives an invalid reference on master. But changing all the images on all deployment to v2.10.9 with the latest helm chart does work for me.
Checklist:
argocd version
.Describe the bug
Related to #18120 case, after upgrade to Argocd Chart 6.9.1 (app 2.11.0) from 6.7.18 (app 2.10.9) the error "resolv repo version" is shown during a manual sync. After apply a downgrade to 6.7.18 it works properly. The same problem with 6.8.x (also app 2.11.0) Chart version.
To Reproduce
When a manual sync starts the error is shown in a pop-up.
Expected behavior
It should starts to sync all components, if any of them has changes to apply. It only works when at least chart version 6.7.18 (app 2.10.9) is deployed.
Screenshots
Version
Versions affected 6.8.x and 6.9.x:
Last version without this problem:
Logs
The text was updated successfully, but these errors were encountered: