-
Notifications
You must be signed in to change notification settings - Fork 90
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
Plugin crash with "set item just set doesn't exist" #277
Comments
Unfortunately your description is not sufficient to enable us to figure out what is causing this issue. Please could you provide the Terraform configuration/code for the affected |
Hey @onematchfox! Thanks for your quick response! Posting the TF file I'm using, hope it helps:
I'm using this module dynamically for multiple deployments, and it works for some deployments ... weird. |
Thanks for supplying the config. Unfortunately, even with this, I have been unable to reproduce this error. There also doesn't seem to be much information out there regarding why this may occur. I did find a similar issue in the Kubernetes provider, which resulted from a block containing a single attribute where the value was set to
If it works for some and not others, then this does feel like a configuration issue. Are you able to reproduce this consistently? |
Thanks for helping on this @onematchfox! Of the 10+ deployments I have 2 are getting this failure consistently, will keep investigating and post an update here on my findings, will close this issue for now 🚀 |
Ok great. I look forward to hearing more. If you do manage to figure out what is causing this then I'd love to make sure we fix the issue. |
I now also see this error in our env at @swisspost.
Since I only see this error on one of our ~45 k8s clusters I suspect something in our env (it's the dev/sandbox cluster where every engineer is doing nasty stuff). I will keep you posted if I find out something. |
ahaaaa 💡 i reproduced it. Then the INFO field was removed inside the UI but it was still present in the App spec: apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
creationTimestamp: "2023-03-09T10:18:25Z"
generation: 147673
name: aqua
namespace: argocd
resourceVersion: "xyz"
uid: xyz
spec:
destination:
namespace: xyz
server: https://kubernetes.default.svc
ignoreDifferences:
- group: apiextensions.k8s.io
# ...
info:
- name: "" # <---------------------------------------------------- see here
value: "" # <---------------------------------------------------- see here
project: swisspost-xyz
revisionHistoryLimit: 10
source:
helm:
valueFiles:
- values.yaml
# ... As soon as I edit the manifest via kubectl and remove these three lines info:
- name: "" # <---------------------------------------------------- see here
value: "" # <---------------------------------------------------- see here , everything is working again. Maybe if you have time @onematchfox you could have a look as you are familiar with the code base :-) |
Nicely done sir! And thanks for the PR. Will try to take a look tomorrow. |
Terraform Version, ArgoCD Provider Version and ArgoCD Version
Affected Resource(s)
Panic Output
The text was updated successfully, but these errors were encountered: