Skip to content
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

Container registry reverts to default on app version change #10703

Open
kravciak opened this issue Mar 27, 2024 · 2 comments
Open

Container registry reverts to default on app version change #10703

kravciak opened this issue Mar 27, 2024 · 2 comments
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@kravciak
Copy link

Setup

  • Rancher version: 2.8.2
  • Rancher UI Extensions: Kubewarden 1.4.1
  • Browser type & version: Chrome 121.0.6167.139 & Firefox

Describe the bug
When I change app version during upgrade process container registry is changed. It's fixed only after page reload.

To Reproduce

Screencast.from.2024-03-27.09-43-53.webm
@github-actions github-actions bot added [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed [zube]: To Triage labels Mar 27, 2024
@torchiaf
Copy link
Member

torchiaf commented Mar 27, 2024

Thanks @kravciak
I couldn't reproduce it in 2.8.2 but I have a different behavior; after kubewarden 2.0.9 is selected, the 'Container Registry' checkbox become unchecked.

image

It requires further investigations.

@kravciak
Copy link
Author

Hi Francesco, thanks for checking. I see the behavior you described too, the difference is only in prime vs community:

  • rancher prime replaces value with system-default-registry (in video)
  • rancher community has no default registry (unchecked checkbox)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

4 participants