-
Notifications
You must be signed in to change notification settings - Fork 375
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
Error when upgrading to v0.34 and up - "panic: recursive set of Transformers detected" #1769
Comments
Have you tried upgrading to another version, like |
Yes, the same error seems to be present in all versions above |
Can you provide the YAML resources you have used to reproduce this issue? |
Unfortunately I have around 1000 different YAML resources and currently don't know which of them are causing the issue |
Then I would suggest, you debug the provider locally against your cluster and see where exactly it panics. |
any option to update to a newer version ? |
Closing due to staleness. Feel free to reopen if something changes. |
This is happening to us as well but only for the "Role" kind, did you end up finding what was causing your issue? |
@fabioaraujopt can you give us a YAML that is causing the crash at your end? |
I also see this kind of logging in the crossplane-contrib/provider-aws pod logging. We are currently on version v0.46.0.
...
note this part:
maybe it hints to location of the problem The pods keeps running, when provided with resources, but is becoming a problem for our logging license. |
What happened?
When upgrading Crossplane from
v0.33.0
tov0.34.0
(using the command:kubectl patch provider.pkg crossplane-provider-aws -p '{"spec":{"package": "crossplanecontrib/provider-aws:v0.34.0"}}' --type=merge
), the crossplane-provider-aws pod goes into a CrashLoopBackoff with the following error:How can we reproduce it?
This consistently happens for us when upgrading from version
v0.33.0
to versionv0.34.0
and is resolved when downgrading back tov0.33.0
What environment did it happen in?
Crossplane version: v0.34+
Kubernetes version: 1.24.13
The text was updated successfully, but these errors were encountered: