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

[v2.10.0] Unable to Edit Config of imported Azure AKS cluster #12525

Open
thehejik opened this issue Nov 6, 2024 · 3 comments · Fixed by #12532
Open

[v2.10.0] Unable to Edit Config of imported Azure AKS cluster #12525

thehejik opened this issue Nov 6, 2024 · 3 comments · Fixed by #12532
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this status/release-blocker
Milestone

Comments

@thehejik
Copy link

thehejik commented Nov 6, 2024

Setup

  • Rancher version: v2.10.0-alpha7 Dashboard: v2.10.0-alpha5 (also on current v2.10-head)
  • aks-operator version: rancher-aks-operator:105.0.0+up1.10.0-rc.2
  • Browser type & version: any

Describe the bug
When attempting to edit/upgrade an imported Azure AKS cluster via Edit Config, the dialog is blank. This dialog is sometimes shown but in this case it offers an empty list of Kubernetes versions to upgrade to with only entry No options instead of any k8s version.

I was able to reproduce this twice in a row on a fresh clusters and with AKS clusters in different locations / k8s versions installed.

It works fine for rancher provisioned AKS clusters.

I believe this is related to the UI, but I may be wrong, in this case please move to CAPI & HP project .

To Reproduce

  • Provision an AKS cluster via az CLI:
az group create -l eastus -n th-rg
az aks create --resource-group th-rg --no-ssh-key --kubernetes-version 1.29 --name th-az-imported-293 --node-count 1 --location eastus
  • Import the AKS cluster into rancher -> Cluster Management -> Import Existing -> Azure AKS, select/create the credentials -> select the cluster you created from the list -> press Import button
  • After a short while the cluster will be imported
  • From Cluster Management select the cluster's three dots vertical menu and select Edit Config

Result

  • The Edit dialog is blank - only sometimes offer a list of k8s versions to upgrade to but there is only No options "version" available.

Expected Result
The Edit dialog should be shown and it should offer a list of valid k8s versions for upgrade

Screenshots
aks-imported-upgrade

image

@thehejik thehejik added this to the v2.10.0 milestone Nov 6, 2024
@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 6, 2024
@rak-phillip rak-phillip self-assigned this Nov 6, 2024
@rak-phillip
Copy link
Member

@thehejik I'm seeing the following error logged to the console

TypeError: Invalid Version: 1.29
    u semver.js:38
    i compare.js:3
    i gt.js:2
    t CruAks.vue:542
    aksVersionOptions CruAks.vue:538
    run reactivity.esm-bundler.js:190
    get value reactivity.esm-bundler.js:1171
    get runtime-core.esm-bundler.js:3488
    get runtime-core.esm-bundler.js:3132
    default CruAks.vue:1062

Can you confirm that you see the same?

@rak-phillip
Copy link
Member

Updating milestone to 2.11 and creating a backport pr for 2.10

@rak-phillip rak-phillip modified the milestones: v2.10.0, v2.11.0 Nov 6, 2024
@rak-phillip
Copy link
Member

/backport v2.10.0

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 status/release-blocker
Development

Successfully merging a pull request may close this issue.

2 participants