We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checklist:
argocd version
Describe the bug
After upgrading Argo CD to v2.2.2+unknown routes are stuck in "Progressing" state.
v2.2.2+unknown
To Reproduce
I have tried the following
Expected behavior
The route health check state is "Healthy"
Screenshots
Version
Unfortunately I don't have access to the server cli, but here's the json output from the Web interface.
{ "Version": "v2.2.2+unknown", "BuildDate": "2022-01-26T02:18:29Z", "GitTreeState": "clean", "GoVersion": "go1.16.12", "Compiler": "gc", "Platform": "linux/amd64", "KsonnetVersion": "unable to determine ksonnet version: exec: \"ks\": executable file not found in $PATH", "KustomizeVersion": "v4.2.0 1970-01-01T00:00:00Z", "HelmVersion": "v3.7.1+gbf78984", "KubectlVersion": "v0.22.2", "JsonnetVersion": "v0.17.0" }
Logs
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
Tagging some co-workers for FYI reference
Sorry, something went wrong.
@ishitasequeira Can you please take a look at this?
@rhblind Check release v2.2.3
Bug Fixes - fix: route health check stuck in 'Progressing' (#8170)
@dnskr Ah, thank you very much! Missed that one!
Fixed with #8170
No branches or pull requests
Checklist:
argocd version
(only json output, sorry).Describe the bug
After upgrading Argo CD to
v2.2.2+unknown
routes are stuck in "Progressing" state.To Reproduce
I have tried the following
Expected behavior
The route health check state is "Healthy"
Screenshots
Version
Unfortunately I don't have access to the server cli, but here's the json output from the Web interface.
Logs
The text was updated successfully, but these errors were encountered: