referenced ImageRepository has not been scanned yet error since upgrade to 2.6.0

[tarioch]

Since the upgrade to 2.6.0 I'm now always getting the following error notifications

referenced ImageRepository has not been scanned yet

I get this also if I manually reconcile an image repository. The log entries look like this

2025-05-29T23:31:01.420Z info ImagePolicy/fava.flux-system - Latest image tag for tarioch/fava resolved to 20250526042245993788 (previously tarioch/fava:2025052319293497a096)
2025-05-29T23:31:01.432Z error ImagePolicy/fava.flux-system - referenced ImageRepository has not been scanned yet DependencyNotReady
2025-05-29T23:31:02.179Z info ImageRepository/fava.flux-system - no new tags found, next scan in 1h0m0s
2025-05-29T23:31:02.184Z info ImagePolicy/fava.flux-system - Latest image tag for tarioch/fava resolved to 20250526042245993788 (previously tarioch/fava:2025052319293497a096)
2025-05-29T23:31:02.195Z info ImagePolicy/fava.flux-system - Latest image tag for tarioch/fava resolved to 20250526042245993788 (previously tarioch/fava:2025052319293497a096)

So while it shows this error it still seems to be work correctly. It looks also like all flux resources are in ready status, so what am I missing, why is it generating this error?

[matheuscscp]

The error is not harmful, that's because when image-reflector-controller starts reconciling an ImageRepository it marks the object as "Progressing", which is not "Ready". The ImagePolicy reconciler gets notified about this change in the ImageRepository status and tries to reconcile, but because the ImageRepo is not ready, we mark the ImagePolicy as not ready either with the reason DependencyNotReady. But when the controller finishes reconciling the ImageRepo, the ImagePolicy will get another event and reconcile properly. You can configure your Alert to ignore this error for now:

https://fluxcd.io/flux/components/notification/alerts/#event-exclusion

[matheuscscp]

Closing as duplicate of fluxcd/image-reflector-controller#773