-
Notifications
You must be signed in to change notification settings - Fork 321
Cluster provisioning node/machine pool vertical tabs are dynamically sorted alphabetically #17122
Copy link
Copy link
Open
Labels
QA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/aksarea/dashboardarea/eksarea/gkekind/bugneeds-info
Milestone
Description
Setup
- Rancher version: 2.15-head
- Rancher UI Extensions: n/a
- Browser type & version: ff
Describe the bug
In all cluster provisioning forms with vertical tabs, the tabs are sorted alphabetically; therefore, when machine/node group names are changed, the tab order may change.
To Reproduce
- Go to ec2 rke2/k3s cluster creation page
- Add a second node group and select its tab
- Rename the node group 'bbb'
- Rename the node group 'zzz'
Result
The node group's tab moves to the top of the stack when it is renamed 'bbb.' When it is renamed 'zzz' it moves to the bottom of the stack
Expected Result
Node groups should appear in the vertical tabs in the order they were added to the cluster regardless of their name
Screenshots
Additional context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
QA/dev-automationIssues that engineers have written automation around so QA doesn't have look at thisIssues that engineers have written automation around so QA doesn't have look at thisarea/aksarea/dashboardarea/eksarea/gkekind/bugneeds-info