-
Notifications
You must be signed in to change notification settings - Fork 71
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
HelmRelease file not updated #214
Comments
Could this be related to #209? have you seen any timeout logs? |
@stefanprodan I think that this just happened again. Following is the data that I was able to collect. |
I see no timeout in the logs. Here is the complete log: Here is the current date: Here is the image policy: |
Pod that lists image deployed: |
Here is the source of the Helmrelease:
Here is the in cluster representation of the helm release: |
Here is the image automation pod: |
What would happen if the controller ran on a node that was very low of memory? Could it cause this failure? |
If you set |
Hi, After forced image-automation-controller restart changes are commited and pushed to repo and application is updated. We've found no information in logs that could tell us anything about the cause and about the problem itself. |
The image-automation controller version v0.21.0 introduces an experimental transport that fixes the issue in which the controller stops working in some specific scenarios. The experimental transport needs to be opted-in by setting the environment variable This will require a redeploy of all components so I would recommend doing so via Can you test it again with the experimental transport enabled and let us know how you get on please? |
Closing this issue due to inactivity, but happy to reopen in case of reincidence whilst using the latest versions of the image automation controller. |
@stefanprodan As you know, I have been using your tools for a long time. My general experience is that the tools are rock solid.
Today a colleague reported that an image was not being updated. I inspected our cluster. The Image Automation controller had been running for 4 days. It had made updates as recently as last night. There were no error messages in the logs. In other words, from the perspective of the Image Automation controller, everything was running fine.
I looked for an ImagePolicy for the image in question. I found one. The policy had been updated to the new image hours earlier. The annotation to instruct the Image Automation controller was attached to a HelmRelease. That file had not been modified with the new image tag. However, that file had been updated by the image automation controller in the last 4 days.
I restarted the Image Automation controller and it quickly updated the Gitlab repo to reflect the proper version of the Image tag.
So, I am left to conclude that either an error occurred that was not properly logged or there is another bug.
The text was updated successfully, but these errors were encountered: