-
Notifications
You must be signed in to change notification settings - Fork 562
chart go-getter git fetch fails if cache is empty #1660
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
Comments
@kirrmann Thanks for reporting! I haven't tried this with 0.137.0 but at least it didn't work for me as well with 0.138.x, as @kevin-lindsay-1 has also reported in #1664. After a bit of investigation, it seems like this is a regression introduced via https://github.com/roboll/helmfile/pull/1629/files#diff-7e4e87a1e777423a3d9a915e00fb78a9c4fc2f4c476863f60b67e89b9c635697R990 |
@kirrmann JFYI, I couldn't reproduce this with the below setup:
I'm still working on #1667 that should fix #1664 for v0.138.x. |
Hi, thanks for your fast response. I took another look at it. I can only cleanly reproduce it if I have two releases defined, both with the go-getter pointing to the same git repo, but not necessarily the exact same url. It works if I filter the releases with
Btw: 0.138.2 doesn't work at all for me
|
I tested older releases and I think this isn't a regression. Even with 0.125.0 this issue shows up. |
@kirrmann Thank you so much for your support! That's super helpful. I'll try to fix it soon 👍 |
I just tested #1669 and it fixes the issue 👍 thanks |
@kirrmann Thanks for confirming! I've released v0.138.4 for it. |
Hi,
latest version 0.137.0 fails to fetch a chart git repo (go-getter style). Error states that it's because the folder/cache already exists or cannot unlink directory. Running helmfile a second or third time fixes this error. Error is reproducible if I delete helmfile.d directory
helmfile:
First run:
Second run (not always but often):
If I define in releases another chart go-getter for the same git repo I hit both errors at the same run.
Subsequent runs work without issue.
The text was updated successfully, but these errors were encountered: