flux2: HelmRepository stuck on "reconciliation in progress"

I tried adding the following:

---
apiVersion: source.toolkit.fluxcd.io/v1alpha1
kind: HelmRepository
metadata:
  name: ingress-nginx
  namespace: gitops-system
spec:
  interval: 1m
  url: https://kubernetes.github.io/ingress-nginx
---

Nothing interesting from the logs:

{
  "level": "info",
  "ts": "2020-09-19T15:44:21.605Z",
  "logger": "controllers.HelmRepository",
  "msg": "Reconciliation finished in 164.626884ms, next run in 1m0s",
  "controller": "helmrepository",
  "request": "gitops-system/ingress-nginx"
}

But when I do kubectl get helmrepository:

NAME            URL                                                READY     STATUS                                             AGE
ingress-nginx   https://kubernetes.github.io/ingress-nginx         Unknown   reconciliation in progress                         4m35s
nextcloud       https://nextcloud.github.io/helm/                  True      Fetched revision: 2020-08-26T16:22:56.644290771Z   106m
bitnami         https://charts.bitnami.com/bitnami                 True      Fetched revision: 2020-09-19T14:51:05.445858887Z   106m
stable          https://kubernetes-charts.storage.googleapis.com   True      Fetched revision: 2020-09-19T15:28:46.2113521Z     6m38s

It’s stuck on Unknown with reconciliation in progress.

If I run gotk reconcile source helm ingress-nginx https://kubernetes.github.io/ingress-nginx:

► annotating source ingress-nginx in gitops-system namespace
✔ source annotated
◎ waiting for reconciliation
✗ context deadline exceeded

This happens with any new repositories I try to add. Only the three currently with “Ready” as True are functional.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

Yup, looking good! I’ve tested it out a bit and I can’t reproduce the issue I was having.

@sseneca please try the following image which has the patch from the above PR: hiddeco/source-controller:resource-statuses-13541f14

Can you simply try to kick the source-controller pod?