flux2: Failed to verify integrity of artifact: artifact has no digest
Describe the bug
Ever since updating from Flux 0.41 to 2.0.1, I’ve been getting these messages sent to my Slack/Discord webhooks everytime it finds and stores a new commit artifact:
gitrepository/flux-system.flux-system
failed to verify integrity of artifact: artifact has no digest
Is there a reason why this shows up? It seems to show up across 6 different Kubernetes clusters, all upgraded from 0.4x versions to 2.0.1.
Steps to reproduce
- Install Flux
- Add Slack or Discord webhook notifications
- Add a GitRepository
- Push to said GitRepository and wait until Flux sees it
Expected behavior
No integrity message shown.
Screenshots and recordings
No response
OS / Distro
N/A
Flux version
2.0.1
Flux check
► checking prerequisites ✔ Kubernetes 1.27.4+k3s1 >=1.24.0-0 ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v0.35.0 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.35.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.29.1 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v1.0.1 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v1.0.0 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v1.0.1 ► checking crds ✔ alerts.notification.toolkit.fluxcd.io/v1beta2 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1 ✔ helmcharts.source.toolkit.fluxcd.io/v1beta2 ✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1 ✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2 ✔ imagepolicies.image.toolkit.fluxcd.io/v1beta2 ✔ imagerepositories.image.toolkit.fluxcd.io/v1beta2 ✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta1 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ providers.notification.toolkit.fluxcd.io/v1beta2 ✔ receivers.notification.toolkit.fluxcd.io/v1 ✔ all checks passed
Git provider
GitLab (self-hosted), GitHub
Container Registry provider
No response
Additional context
No response
Code of Conduct
- I agree to follow this project’s Code of Conduct
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 15 (10 by maintainers)
I’ve update the GA upgrade procedure to include API bumps in
Receiver.spec.resources, thanks @clrxbl for catching this.@L3o-pold please see if this fixes the issue for you as well.
@stefanprodan seems to fix 🎉 ❤️