no changes made in working directory; no commit for Image Automation

[shalineekaran]

          Getting:

no changes made in working directory; no commit

Originally posted by @rayterrill in #159 (comment)

[shalineekaran]

@kingdonb

[shalineekaran]

@rayterrill Please help how you managed to fix it.. I am unable to

[kingdonb]

Please provide more information. We cannot verify this is a bug without details about your deployment.

We had multiple reports of issues with the Flux Image Automation Controller that turned out to be some user error. For example yesterday we went through this issue with a person in #flux who ultimately came to the conclusion that their kyaml markers were malformed, using a / instead of a : in the image policy selector.

Any detail could be important.

If there is a bug here, it is better classed as a usability issue, because Image Automation Controller doesn't emit errors when there is no match. Because of the tree shape and nature of the image controller, we can't know when there is a not-matching tag that it doesn't belong to some other image automation resource tree.

[kingdonb]

A starting point for debugging is in the old Flux v1 migration guide, Image Automation Troubleshooting:

https://fluxcd.io/flux/migration/flux-v1-automation-migration/#troubleshooting

If you wish to engage the community support for debugging your flux image automations, a better way is joining the CNCF slack and posting a thread in the #flux channel there. We have commercial as well as community support options documented here:

https://fluxcd.io/support/#getting-flux-support

See the sub-heading "Getting help from the Flux Community" there. If you solve your issue with these debugging guides, please remember to post the resolution here.

[makkes]

Duplicate of #159. Please use Slack or GitHub Discussions for support requests.