after master update node pool does not offer any upgrade

[Morriz]

I just reported an issue about autoscaler not working due to invalid VMS due to mismatch in version support here: #2262

Now, this might be related: We consistently observe that aks clusters that get patch upgraded from an unsupported version to the latest supported patch version do NOT offer a node pool upgrade above its current running version, even after the vms have successfully cycled into "latest" mode.

What you expected to happen:

same version as master to be offered for node pool upgrade

How to reproduce it (as minimally and precisely as possible):

• Run aks cluster with "standard" node pool without auto upgrade until it slides out of range of supported patch versions.
• Upgrade cluster version to latest patch version
• Observe/helm vmms to cycle nodes
• Try to upgrade node pool and observe there is no upgrades offered at all

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): irrelevant, problem occurs unrelated to version
• Size of cluster (how many worker nodes are in the cluster?) 8 out of 9 max

[ghost]

Hi Morriz, AKS bot here 👋
Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such:

1. If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
2. Please abide by the AKS repo Guidelines and Code of Conduct.
3. If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
4. Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
5. Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
6. If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

[ghost]

Triage required from @Azure/aks-pm

[ghost]

Action required from @Azure/aks-pm

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Action required from @Azure/aks-pm

[palma21]

Which kubernetes version was your control plane and nodepool in before the upgrade?

I just tested in a nodepool running 1.18.17 (unsupported) and control plane running 1.19.11 (supported) and when I ran

az aks nodepool get-upgrades it returned 1.19.11 as possible upgrade as expected.

[ghost]

This issue will now be closed because it hasn't had any activity for 7 days after stale. Morriz feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.