-
Notifications
You must be signed in to change notification settings - Fork 37
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
Argocd application creation fails #136
Comments
@maximilianbraun @janwillies - Is this something you can help me out with? |
This seems to be a permission error that is returned by Argocd if a Which Argocd version are you using? And can you try it with provider-argocd |
I tried it and it returns same
|
@aslamkhan138 which argocd version do you ahve deployed? |
I have tried on both v0.5.0 and v0.6.0 |
@aslamkhan138 and which version of argo-cd itself are you running? |
@maximilianbraun - argocd version : v2.6.7+5bcd846 |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
What happened?
Argocd application creation fails with error
observe failed: cannot list Argocd application: rpc error: code = NotFound desc = application 'example-application-kubeconfig' not found
How can we reproduce it?
Apply this manifest https://github.com/crossplane-contrib/provider-argocd/blob/release-0.5/examples/application/application.yaml.
What environment did it happen in?
Crossplane version: v0.39.0
Crossplane Provider argocd version: v0.5.0
I see we are hitting this: https://github.com/crossplane-contrib/provider-argocd/blob/release-0.5/pkg/controller/applications/controller.go#L113. Ideally, do we need to set nil instead of error there?
The text was updated successfully, but these errors were encountered: