-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple empty commits since flux2 v0.37 #466
Comments
Thank you for reporting this @srgvg. I have been trying to reproduce this in the last hour with no luck so far. (cc @aryan9600) |
hi @srgvg, could you also please share the relevant |
|
Just found out that I disabled earlier the The
About 3 minutes later, it makes again 3 empty commits. Relevant logs are
After that again after ~2-3 minutes. This seems to match the aforementioned Currently:
Notice those 49 tags are the same amount as before those commits (confirming no new tags were detected), the image policy mentions the latest detected tags datecoded on November 7. In all of this setup, tehere are only 2 places with a imagepolicy tag (also as aforementioned, |
I set log level to debug on both At and after restart I now get for the
and for the
|
Changes required upstream in order to avoid the creation of empty commits: go-git/go-git#623 fluxcd/go-git#11. Further investigation still needed to understand why this is happening. |
@srgvg I have created a RC image which blocks the empty commits from being created: It will simply log an error in the controller instead of creating empty commits. So at least other automations you have would be able to work normally. |
@srgvg Does the repo where you observed this behaviour, have any of the below?
|
None. I does have a couple of |
Done & verified
Seems like only a partial fix. Where I had 3 commit's in a row every
|
@srgvg Are the empty commits still created in the target repository? Does the controller log any errors? |
Yes, same empty commits - except 2 per batch instead of three per batch like formerly. Logs were attached, not sure what extra information you are aiming on? |
@srgvg we have just released a new RC, can you please retest and confirm whether it solves your issue? |
using I'm afraid the same problem still persists:
enabled debug logging on the automation controller:
showing that last referenced commit:
|
Can confirm I am seeing the exact same behavior.
|
@devopstagon what Git server are you using? Any further information you can provide, as we are still not able to fully reproduce this. @srgvg @devopstagon we are making changes to fix another issue on IAC. Do you mind trying to reproduce the issue with this image please: |
Not solved with image automation logs:
Although, in z couple of minutes there were 3 commits, 1 first, and then some minutes later two other, only 4 seconds apart....
Let me know if I can provide more info. |
The next "run" I see again 3 commits, though not all at the same exact second
|
@srgvg found another execution path that could be leading to this. Here's an image with the fix: |
@pjbgf To be clear I am using GitLab. That being said I tested the fix and it does indeed solve the issues. I have had 0 commits now after 20 minutes. Will leave it overnight and see. |
Looks like this is solved now, indeed.
30 minutes later and still nothing. Sounds like solved. |
Excellent, thank you @devopstagon and @srgvg for testing it and reporting back. We will soon release an official version with the fix. |
Thank you for your work. Looking forward! |
The new official image automation controller image contains the fix: |
I am facing the similar issue where without any new changes , flux is committing to git in every 1min(in my case). installed versions : |
@SonalinP well, yes, upgrade Flux to |
Initially discussed in slack
This started after upgrading to
0.37
:I get such a commit like every 5s
At some point, restarting the image-automation controller stopped that, however some time later it had restarted again. I think I experienced that twice, however not realising exactly enough what was happening, I didn't keep any logs from this controller, unfortunately.
This is the same base git repo that flux kustomize uses, happens on the master branch, hosted in Gitlab. Verified there were no commits in the container image gerenrating git commit that would have warranted any update. The latest actual image version, gitlab pipeline and latest git commit are all related, and several days older than aforementioned flux2 upgrade. All git authentication happens through an SSH keypair.
Relevant automation manifests:
example of a correct commit
I will monitor this more closely, and get back here with more info, and hopefully some more relevant logs.
The text was updated successfully, but these errors were encountered: