-
Notifications
You must be signed in to change notification settings - Fork 256
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
Chart Repository refresh does not actually refresh the chart repo #7668
Comments
This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions. |
bump |
Checking how much of this is UI related. If so, will transfer to |
From my tests it looks like it's backend. If all I do is refresh after the repo has been updated I see the request get made and the repo status cycles through until it gets back to active. If you clone a repo and give it a new name and refresh the updates show up. It makes me think that the backend is caching something based on the repo name. |
@Jono-SUSE-Rancher or @MKlimuszka I'll allow you to find a backend engineer to look into this. |
End-user complaints(noticed) a similar issue in 2.6.3 : |
I'm using the same Rancher version: v2.6.3 and Kubernetes version: 1.21.7. We store our charts in S3 and Harbor. I'm encountering a slightly different problem. When I select a chart to install, I expect to see the latest/new version (11160.1.48) but it does not show under the Chart Versions. I also found 2 workarounds. Workaround rancher/rancher#1: I have to do it in the EXACT order: Step 2: Apps & Marketplace>Charts - Refresh chart-repo. Workaround rancher/rancher#2: Apps & Marketplace>Charts - Refresh chart-repo TWICE In my case, I need to automate (script) refreshing repo/chart. Going for workaround rancher/rancher#2, I use Developer Tools to capture the URL and request and response. I notice the request looks similar to the response.
I use SoapUI and curl commands to mimic what Rancher UI does.
In Rancher UI, I select a chart to install, the latest/new version does not show under the Chart Versions. Any help is greatly appreciated! |
I tried the latest version:v2.6.9, this problem is still found, |
When will this bug be fixed? My work is blocked by this bug |
I worked on this issue with @pennyscissors. It turned out that this actually was a front end issue. The |
…updated The catalog.cattle.io.clusterrepos/{repo} resource doesn't subscribe to updates. We now force a full request in the areas where it's appropriate to do so. fixes rancher#7668
Related tech debt issue #7963 |
retest passed, moving to done tested on: testing efforts taken:
|
Rancher Server Setup
Information about the Cluster
User Information
Describe the bug
The refresh button
does not actually sync the latest changes from the repo to rancher.
To Reproduce
Result
Chart is deployed with old version
Expected Result
Chart to be deployed with latest changes on the branch after a refresh
Screenshots
Additional context
The only way is the create a new repo on rancher with a different name. Deleting and creating a repo with the same name does not fix the issue, you still have the old, cached version of the chart.
Is there even a automated periodic refresh at all?
The text was updated successfully, but these errors were encountered: