Skip to content
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

Bootstrapping to Latest Causing Git Clone To Failed #438

Closed
brianpham opened this issue Sep 15, 2021 · 3 comments
Closed

Bootstrapping to Latest Causing Git Clone To Failed #438

brianpham opened this issue Sep 15, 2021 · 3 comments

Comments

@brianpham
Copy link

brianpham commented Sep 15, 2021

Not sure why cloning repository is failing after bootstrapping. This is the error that I am seeing when trying to reconcile manually. My staging cluster is still able to clone the repo and is using the same deploy key as dev.

► annotating GitRepository bpham-firespotter in flux-system namespace
✔ GitRepository annotated
◎ waiting for GitRepository reconciliation
✔ GitRepository reconciliation completed
✗ GitRepository reconciliation failed

This is the error that I am seeing on the flux-controller. Can anyone help with where I should look? It doesn't seem to be an auth issue from what I can tell.

{"level":"error","ts":"2021-09-15T23:46:08.197Z","logger":"controller.gitrepository","msg":"Reconciler error","reconciler group":"source.toolkit.fluxcd.io","reconciler kind":"GitRepository","name":"bpham-firespotter","namespace":"flux-system","error":"unable to clone 'ssh://git@github.com/dialpad/firespotter', error: context deadline exceeded"}

Components
flux version 0.17.1
app.kubernetes.io/version: v0.14.2 to v0.17.1
controller-gen.kubebuilder.io/version: v0.4.1 to v0.5.0
helm-controller:v0.10.1 to v0.11.2
kustomize-controller:v0.12.2 to v0.14.1
notification-controller:v0.14.1 to v0.16.0
source-controller:v0.13.2 to v0.15.4

EDITED: I tested by rolling back the source controller back to v0.13.2 and that works.. Then I bumped it to v0.14.0 and ran into the same error above (context deadline exceeded). Seems like something broke here for me. Maybe related to this change? #372

@stefanprodan
Copy link
Member

Can you please set the spec.timeout to something like 60s and see if it works?

@brianpham
Copy link
Author

Yeah that seems to work if I set it in the spec. @stefanprodan, weird I was suspecting that was the issue. I forgot to mention that I ran flux reconcile git source bpham-firespotter --timeout 10m with no luck so I didn't try putting it in the spec.

@stefanprodan
Copy link
Member

The reconcile command doesn’t alert objects in you cluster. If you want to change the spec.timeout you need to do it your repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants