-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
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
Apps in Any Namespace: Warnings thrown when viewing application in UI #13694
Comments
Thank you for reporting! Fixed by #13664 |
I just upgraded to latest with this bug fix, and I am still receiving the same error. It looks like the server is looking in the wrong namespace for the application resource. |
Hey. We have the same issue with latest version |
This issue is also present for manifest editing not only on links field. |
For manifest editing this was fixed in #13839 |
@crenshaw-dev here the issue is a similar but needs bit more work as appNamepace is not even part of the query in the proto. I can take care of it today |
Yes all good on my side since upgrade to 2.7.7 |
…j#13890) Signed-off-by: Geoffrey Muselli <geoffrey.muselli@gmail.com> Co-authored-by: Geoffrey MUSELLI <geoffrey.muselli@gmail.com> Signed-off-by: schakrad <58915923+schakrad@users.noreply.github.com>
Signed-off-by: Geoffrey Muselli <geoffrey.muselli@gmail.com>
Signed-off-by: Geoffrey Muselli <geoffrey.muselli@gmail.com>
Describe the bug
When running ArgoCD with application-namespaces, if an application is created in another namespace, and then viewed in the UI, an error pops up as seen below in screenshots.
The links field fails to load, and checking the logs, it looks as if the server is looking for the application in the argocd namespace, even though it is in another namespace.
level=warning msg="application does not exist" application=xxx namespace=argocd
Checklist:
argocd version
.To Reproduce
metadata.namespace
anything other than argocd (to match exactly, this was done tracking resources in a private repo)Expected behavior
Screenshots
Version
Logs
The text was updated successfully, but these errors were encountered: