Helm-operator: Release does not belong to HelmRelease, this may be an indication that multiple HelmReleases with the same release name exist.

[mar1n3r0]

Describe the bug
A clear and concise description of what the bug is.
The automated deployment stopped working. The status of the helmRelease is deployed but it doesn't detect changes in image versions from docker repository.
To Reproduce
Steps to reproduce the behaviour:
https://github.com/fluxcd/helm-operator-get-started

Expected behavior
The automated releases based on image versions to work.
Logs
If applicable, please provide logs. In a standard stand-alone installation, you'd get this by running kubectl logs -n default deploy/flux-helm-operator.

textPayload: "ts=2019-10-21T13:17:31.407051541Z caller=chartsync.go:374 component=chartsync warning="release 'office-hub-stg' does not belong to HelmRelease, this may be an indication that multiple HelmReleases with the same release name exist" resource=stg:helmrelease/office-hub-stg

Additional context
Add any other context about the problem here, e.g

• Helm operator version: 1.14.2
• Kubernetes version: 1.13.7-gke.24
• Git provider: Bitbucket
• Container registry provider: Docker Hub

[hiddeco]

Helm operator version: 1.14.2

This is likely your Flux version, and not the Helm operator version you are running. There has been a fix (#56) for the behaviour you are describing in the second latest release (1.0.0-rc2).

[mar1n3r0]

Thanks do you know how can I view the Helm operator version currently running ?

[stefanprodan]

We use the version to tag the container image: kubectl -n flux get deploy/flux-helm-operator -oyaml | grep image

[mar1n3r0]

An upgrade to 1.0.0-rc2 did indeed solve the issue. Marking this as resolved.