-
Notifications
You must be signed in to change notification settings - Fork 73
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
v0.10.0 Updates unsuccessful with both implementations #176
Comments
Duplicate of: #172 A fix will be delivered today |
i just rolled back to 0.9.1 of the controller and apparently it doesnt work with it either, not sure how it ever worked ill try the timeout :) |
The repo is actually quite small tbh, thats why im really confused. the bitbucket logs also show 200 status codes for all requests which is also weird… |
@Robbilie there is a new image available that you could try: |
i just tried libgit2 after i fixed a colleague having inserted the wrong update marker -.- i now tried your new image, but it still throws the same error with go-git, libgit2 works though |
@Robbilie can you please verify that the new image has been rolled out in your cluster |
verified and retried with go-git, not working :( can you explain or link, what the issues origin might be? maybe i can assist in analyzing then :) PS: coming from a differnt projects documentation & support the past few days, i really appreciate your support here, amazing :) |
When you say it is not working with |
{"level":"error","ts":"2021-06-02T11:51:55.845Z","logger":"controller-runtime.manager.controller.imageupdateautomation","msg":"Reconciler error","reconciler group":"image.toolkit.fluxcd.io","reconciler kind":"ImageUpdateAutomation","name":"demo","namespace":"services","error":"empty git-upload-pack given"} |
This should've been fixed in |
confirmed working :) |
I currently have 2 gitrepository resources in the cluster. they are both based on repos in a bitbucket server. they both sync perfectly fine.
about a week ago the flux version was updated and thus came 0.10.0 of the automation controller.
since then, the controller logs the following error:
go-git:
{"level":"error","ts":"2021-06-02T10:41:14.166Z","logger":"controller-runtime.manager.controller.imageupdateautomation","msg":"Reconciler error","reconciler group":"image.toolkit.fluxcd.io","reconciler kind":"ImageUpdateAutomation","name":"demo","namespace":"services","error":"empty git-upload-pack given"}
libgit2:
{"level":"error","ts":"2021-06-02T09:06:04.731Z","logger":"controller-runtime.manager.controller.imageupdateautomation","msg":"Reconciler error","reconciler group":"image.toolkit.fluxcd.io","reconciler kind":"ImageUpdateAutomation","name":"demo","namespace":"services","error":"unable to clone 'https://xxx/bb/scm/sulu/sulu_services_config', error: failed to connect to xxx: Operation timed out"}
any ideas where this comes from?
The text was updated successfully, but these errors were encountered: