AKS region changes in Edit Mode

[IsaSih]

Setup

• Rancher version: v2.9-0f2bd9c3cde85aa2b5270946d0cecd5c95b86fd2-head

Describe the bug

When creating an AKS cluster in a region different from the default displayed in the UI (East US) with the wrong configuration, once the user edits the cluster config, the Azure Region is set back to the default, undoing the region that the user previously selected

To Reproduce
1- Via UI, create an Azure cluster under a region other than East US with incomplete or wrong config
2- After the cluster is created, try to edit the cluster config via UI
3 - Observe that the region switches to the East US

Result
the Azure Region is set back to the default, undoing the region that the user previously selected

Expected Result
The region previously selected by the user must be preserved in the Edit form

Screenshots

Screen.Recording.2024-09-05.at.17.24.41.mov

[gaktive]

/backport v2.10.1

[IsaSih]

I'll reopen the issue as the behavior is still not expected. Once the user edits the cluster region when it's still in provisioning mode, the dropdown is available for changes, then the user can choose a different region and Save the changes. However, if the user edits the cluster a second time, the original region selected is locked in the dropdown, with a No options element being displayed and scrolled in the whole page as observed in the screenshot.

Tested in
Rancher | v2.11-a1bda936c809e0394520c9d40d2998529223401e-head
Dashboard | master c987984
Rancher CLI | v2.11.0-rc.1

[IsaSih]

Screen.Recording.2025-01-28.at.16.57.03.mov

[mantis-toboggan-md]

That video looks like expected behavior to me. Region is generally only editable immediately after creating an AKS cluster in Rancher, unless something has gone wrong. The intent is to allow users to fix mistakes if some aspect of their cluster configuration has prevented backing resources in Azure to be created, for whatever reason.

Pretty soon after you create an AKS cluster through Rancher, Rancher will go talk to azure and create AKS resources on your behalf, the state of which are reported back to Rancher (and its UI) in the cluster status field. In the period of time between you initially creating your cluster in the Rancher UI, and when stuff starts being created in azure, you can edit most of the cluster spec. This is the stage at which you are changing the region in your video. Once the cluster status field reports that there are underlying resources created in azure, less of the form is editable. That's the state the cluster is in at the end of your video.