-
Notifications
You must be signed in to change notification settings - Fork 3
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
Crashed w/ runtime error [Observed a panic in reconciler: runtime error: invalid memory address or nil pointer dereference] #1
Comments
Hi @galregev, thanks for finding and opening the issue, I am investigating it. |
…served-a-panic-in-reconciler-runtime-error-invalid-memory-address-or-nil-pointer-dereference fix for issue #1, added event recorder
Hi @galregev, the bug is corrected. Please try it again and let me know if you face any issues with that or anything else in the future. |
Hey @akyriako Thank you for responding. Here is the
And some logs:
|
Hi @galregev, I am sorry you don't have a smooth experience. In the new log that you sent I don't see the old error anymore (it is fixed), but I see something totally different: is forbidden: User "system:serviceaccount:sleepcycles-system:sleepcycles-controller-manager" cannot update resource "deployments" in API group "apps" in the namespace "es-digital-journeys""} That is an RBAC issue. |
…served-a-panic-in-reconciler-runtime-error-invalid-memory-address-or-nil-pointer-dereference fix for issue #1, added RBACs missing
…served-a-panic-in-reconciler-runtime-error-invalid-memory-address-or-nil-pointer-dereference fix for issue #1, time encoder
Fixed |
Hey there 👋🏻
I'm running on AWS EKS cluster v1.25.
The sleepcycles were installed on the cluster and the label were configured on one of the deployments.
Here are some logs from sleepcycles pod:
Here is the output from
**k get sleepcycles.core.rekuberate.io -w**
:🙏🏻 Thanks you in advance, Let me know in case there is some issue template.
The text was updated successfully, but these errors were encountered: