[AKS] Nodepool management misbehaves if initial nodepool is named 'pool1'

[valaparthvi]

Setup

• Rancher version: v2.9-a9355940c0629ca419b7dd3e4098c4ea0e52c0c0-head
• Rancher UI Extensions: master 46a44c1
• Browser type & version:

Describe the bug

If the cluster initially has a single nodepool named 'pool1', subsequently adding/removing another nodepool becomes confusing.

To Reproduce

1. Create an AKS cluster with only nodepool 'pool1'.
2. Once the cluster has provisioned, try adding a new nodepool.

Result
Nodepool with name 'pool1' will be re-added. If you try removing the nodepool, all nodepools are removed.

Expected Result

It should not misbehave when trying to add a new nodepool
Screenshots

Screencast.from.07-10-2024.05.37.30.PM.webm

Also happens when renaming agentpool to pool1 during initial cluster creation.
Screencast from 07-10-2024 05:42:08 PM.webm

Additional context

Workaround:

1. Add another nodepool, pool2 with system mode and update.
2. Once the update is complete, edit the cluster to remove the nodepool 'pool1'.
3. Once this update is complete, nodepool management seems to be back to working as expected again.
4. When a new nodepool is added it will be called 'pool1', and the next one will be called 'pool3'.

[valaparthvi]

@richard-cox @mantis-toboggan-md Can this get some love?

[valaparthvi]

Tested on Rancher: v2.9-81337b95660cba868629d6fe769bd7e8242b5aee-head, Dashboard: master 3da1205.

It is only partially fixed.

I would not say it is blocking anymore, but the behavior can still be improvised.

Screencast.from.07-17-2024.06.05.04.PM.webm

[mantis-toboggan-md]

I thought it could be better as well @valaparthvi but I didn't want to add too much to the 2.9.0 release at this stage so I filed an issue to improve node pool/group naming across the 3 hosted providers #11451

[valaparthvi]

@mantis-toboggan-md In that case, feel free to close this issue and track this in the one you filed.

[izaac]

Tech notes and test coverage details in PR. A manual QA validation will be executed before closing.

[valaparthvi]

I am closing this issue in favor of tracking further enhancements in #11451.

[valaparthvi]

Tech notes and test coverage details in PR. A manual QA validation will be executed before closing.

Manual QA validation is already done, see #11406 (comment).

[izaac]

I missed that comment. please do as needed thanks