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

Upgrade of flux marks all helmreleases as unreconciled #1698

Closed
1 task done
brujoand opened this issue Aug 8, 2021 · 4 comments
Closed
1 task done

Upgrade of flux marks all helmreleases as unreconciled #1698

brujoand opened this issue Aug 8, 2021 · 4 comments

Comments

@brujoand
Copy link

brujoand commented Aug 8, 2021

Describe the bug

When I upgrade the flux version in my cluster by running a new bootstrap every helmrelease will be unreconciled until manually reconciled.

Steps to reproduce

  1. Upgrade flux version by rerunning the bootstrap command
  2. Wait for it to complete successfully
  3. Notice that all helmreleases are now unreconciled
  4. Write bash script to iterate through all helmreleasese an ask flux to reconcile them

Expected behavior

All helmreleases which where reconciled before the bootstrap should stay reconciled after the bootstrap.

Screenshots and recordings

No response

OS / Distro

Ubuntu 20.04

Flux version

0.16.2, just upgraded from 0.16.1

Flux check

► checking prerequisites
✔ kubectl 1.21.1 >=1.18.0-0
✔ Kubernetes 1.20.5 >=1.16.0-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.11.2
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.13.3
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.15.1
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.15.4
✔ all checks passed

Git provider

Github

Container Registry provider

No response

Additional context

This has happened for a while now after upgrades, and I can't find anything interesting in the logs. But it might help if I had some pointers on what to look for.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@brujoand brujoand changed the title Upgrade of flux set's all helmreleases as unreconciled Upgrade of flux marks all helmreleases as unreconciled Aug 8, 2021
@hiddeco
Copy link
Member

hiddeco commented Aug 8, 2021

Can you notice a difference in the Status of a HelmRelease object post-upgrade?

@brujoand
Copy link
Author

brujoand commented Aug 9, 2021

The status just changes to 'namespace/release' is not ready

@nvanheuverzwijn
Copy link

I noticed that if the helm-controller is heavily used, the liveness check may fail and will restart the pod. This may be what is happening.
@brujoand I suggest that you check if the helm-controller pod has restarted. If it has, this may be why you see weird behavior i.e. chart stuck in a deployed state, all helmrelease being unreconciled, etc.
Hope you found out what was going on :)

@stefanprodan
Copy link
Member

Fixed by fluxcd/helm-controller#738

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

4 participants