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

Look at gating mechanism so that Elemental 2.0.0 doesn't run in Rancher 2.10 #12631

Open
aalves08 opened this issue Nov 20, 2024 · 2 comments
Open
Assignees
Labels
area/extensions kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@aalves08
Copy link
Member

Look at gating mechanism so that Elemental 2.0.0 doesn't run in Rancher 2.10. User reported this problem, which breaks their system.

Workaround is to use safemode if Rancher get's "stuck" and not running

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Nov 20, 2024
@aalves08 aalves08 added this to the v2.10.1 milestone Nov 20, 2024
@aalves08 aalves08 self-assigned this Nov 20, 2024
@richard-cox
Copy link
Member

The problem isn't the dashboard's gating mechanism.

  • Rancher 2.10.0 roughly aligns with a shell version of 3.x
  • The latest elemental extension is for 2.9 only but has the annotation "catalog.cattle.io/ui-extensions-version": ">= 2.0.0-0",
  • Rancher 2.10.0 evaluates 3.0 as >= 2.0 so loads the extension

The fix is to update the existing chart. I don't think we can release a new version of the extension as the previous one will still load and we shouldn't be putting 'if extension x with version y don't load' in dashboard if there's a better solution.

@gaktive
Copy link
Member

gaktive commented Nov 21, 2024

There's one report from the community of trying to run Elemental 2.0.0 in Rancher 2.10.0 today so folks are hitting this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions 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

3 participants