-
Notifications
You must be signed in to change notification settings - Fork 72
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
Crash "panic: invalid pointer handle: loop" with EXPERIMENTAL_GIT_TRANSPORT = true #358
Comments
@johnp-stella thank you for creating the issue and sharing the error logs. Can you confirm this is consistent? Does it generally take the same amount of time for it to crash after restart? Does it happen every single time? Does the changes ever get pushed back into the repository? Are you using what SSH key type (e.g. |
1.) It is consistently crashing
2.) The timing is similar but not exact - and does not crash the same point each time
3.) It is pushing changes to repo - as the point it crashes is not consistent so is sometimes able to progress to a push.
|
I tied changing the GitHub ssh key type to ED25519 - Still saw the controller crashing |
I was not able to reproduce this issue yet, but I have made a few changes recently and would be keen to see whether you still experience the same problem in your environment. Here are two images created with latest source controller (which includes panic recovery) plus the removal of ssh connection caching. And the image-automation-controller using said source-controller version:
More details on: |
Thanks @pjbgf The experimental docker images above have fixed the crashing issue. It has been stable and seems to be working as expected. |
Thanks for the information! I'm going to assign this to @pjbgf so it can be closed. 👍 |
When trying out the EXPERIMENTAL_GIT_TRANSPORT we are seeing a crash loop. "panic: invalid pointer handle: loop" when pulling from github.
Have tried the experimental image from #339 without any success.
image-automation-controller debug logs (
The text was updated successfully, but these errors were encountered: