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

v0.14.0 not starting on k8s v1.20.2 and ARM64 #385

Closed
larsha opened this issue Jun 15, 2021 · 8 comments · Fixed by #386
Closed

v0.14.0 not starting on k8s v1.20.2 and ARM64 #385

larsha opened this issue Jun 15, 2021 · 8 comments · Fixed by #386
Labels
area/ci CI related issues and pull requests bug Something isn't working

Comments

@larsha
Copy link

larsha commented Jun 15, 2021

Hi!

I upgraded to Flux v0.15.0 which includes the v0.14.0 of the source-controller. I can't get the pod to start, crashes immediately, no info in logs (tried both error and debug for log-level). I manually changed the image from v0.14.0 to v0.13.2 and it starts without any issues.

Can this be related to ARM64? (I read some info in the release notes regarding some ARMv7 issues?)

It exits with exit code 139, no other info that I can find.

@hiddeco
Copy link
Member

hiddeco commented Jun 15, 2021

It is probably related to ARM64 and the ARMv7 issues we experienced, I even think there is a chance that the ARMv7 patch conflicts with ARM64.

Do you by any chance make use of the automation controllers? If so, do they boot OK (image-automation-controller in particular)?

@hiddeco hiddeco added area/ci CI related issues and pull requests bug Something isn't working labels Jun 15, 2021
@larsha
Copy link
Author

larsha commented Jun 15, 2021

Yes I use them, and image-automation-controller seems to boot up just fine.

@hiddeco
Copy link
Member

hiddeco commented Jun 15, 2021

That gives me sufficient information to look for a solution, or rather, trace why the image-automation-controller succeeds to build without the patch that was required for this controller.

This may take some time, but I'll start tomorrow.

@hiddeco
Copy link
Member

hiddeco commented Jun 15, 2021

In the meantime: dropping the binutils-gold from https://github.com/fluxcd/source-controller/blob/v0.14.0/Dockerfile and rebuilding the image for your architecture should work and temporary resolve the issue.

@larsha
Copy link
Author

larsha commented Jun 15, 2021

Thank you! Let me know if you need anything from me or if I can assist you in some way.

@ViBiOh
Copy link

ViBiOh commented Jun 16, 2021

Same problem here on Kubernetes v1.21.1+k3s1, Manjaro ARM64 on Raspberry pi4.

I have no starting log, the kubectl describe give me this event. I reverted back to 0.13.2. If you need more details, I can give you more ;)

  Normal   Scheduled  60s                default-scheduler  Successfully assigned flux-system/source-controller-54bbf867c6-8jgzs to charlie
  Normal   Pulling    59s                kubelet            Pulling image "ghcr.io/fluxcd/source-controller:v0.14.0"
  Normal   Pulled     39s                kubelet            Successfully pulled image "ghcr.io/fluxcd/source-controller:v0.14.0" in 20.324590933s
  Normal   Pulled     17s (x2 over 33s)  kubelet            Container image "ghcr.io/fluxcd/source-controller:v0.14.0" already present on machine
  Normal   Created    16s (x3 over 35s)  kubelet            Created container manager
  Normal   Started    16s (x3 over 35s)  kubelet            Started container manager
  Warning  Unhealthy  16s (x3 over 34s)  kubelet            Readiness probe failed: Get "http://10.42.1.222:9090/": dial tcp 10.42.1.222:9090: connect: connection refused
  Warning  BackOff    10s (x6 over 31s)  kubelet            Back-off restarting failed container

@hiddeco
Copy link
Member

hiddeco commented Jun 16, 2021

Any chance one of you also has access to an ARMv7 machine? If so, can you please confirm the current image does work on that machine?

@larsha
Copy link
Author

larsha commented Jun 16, 2021

Any chance one of you also has access to an ARMv7 machine? If so, can you please confirm the current image does work on that machine?

I'm afraid I don't have access to an ARMv7 machine.

@hiddeco hiddeco unpinned this issue Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci CI related issues and pull requests bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants