Skip to content

Shell: Chart version is expected to match AppVersion when determining extension upgrade availability #14204

@jtomasek

Description

@jtomasek

Setup

  • Rancher version: 2.11
  • Rancher UI Extensions: 3.0.4
  • Browser type & version: Chrome

Describe the bug
When the UI determines availability of upgrade for the extension it is comparing UIPlugin version with available charts versions. However, when the UIPlugin CR is created, it's version is populated from chart.appVersion.

This can result in incorrect upgrade availability identification in case when chart version and chart appVersion don't match.

To Reproduce
Publish an extension with version e.g. 1.3.1 and then manually change the generated chart version to different version (e.g. 302.0.0+up1.3.1). This is for example used in downstream Edge extensions charts.

Result
As a result when the extension is installed, it immediately suggests an upgrade to a newer version 1.3.1 -> 3.0.2.0.0+up1.3.1. Because UIPlugin version is 1.3.1 (from chart.appVersion) but the newly available version is identified 3.0.2.0.0+up1.3.1 (from chart.version).

Expected Result
The extension is not set as upgradable because UIPlugin version is the same as chart appVersion.

Screenshots

Additional context

Metadata

Metadata

Assignees

Labels

QA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thiskind/bug

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions