The upgrade path shows you can upgrade 5.10 to a maximum of 5.17.1.3 Upgrade Paths

Maybe there is a compatibility thing going on with your hardware of hypervisor. Here you can find the compatibility matrix: Compatibility and Interoperability Matrix

Are any updates showing at all? Does the inventory otherwise look correct showing versions etc?

@Pablo Alejandro LCM won’t show any AOS updates already at the end of Support Life (EOL). 

As per the upgrade path guide (considering LTS releases only), from AOS - 5.10, you cannot directly upgrade to the latest AOS LTS release. Instead, it will be a 2-path upgrade process:

1. AOS 5.10 => 5.15.7 LTS 
2. AOS 5.15.7 LTS => 5.20.4.5 LTS 

However, the first path upgrade to AOS 5.15.7 LTS version won’t be shown in LCM since AOS 5.15.7 AOS went EOL in May 2022, as mentioned on the EOL Information page on Portal. This is why you cannot see any AOS upgrades on Portal. For the same reason, this AOS 5.15.7 version won’t appear as a 1-click download available on the ‘Upgrade Software’ settings page on Prism. 

Hence, in this case, the only way to upgrade AOS to the 5.15.7 version is to upload the metadata and binary files on the ‘Upgrade Software’ settings page on Prism for AOS, and once this is done, you can proceed with upgrading AOS on the cluster. 

Once AOS is at 5.15.7, you can re-run LCM inventory, and it should show up with the 5.20.4.5 AOS LTS upgrade option available. 

You can refer to the following guide for upgrading AOS using the metadata and binary files Upgrading AOS by Uploading Binary and Metadata Files

Kindly let me know if you have any more questions on this one.

Thanks @Nupur.Sakhalkar that’s interesting.

It seems an odd decision to simply hide the releases rather than at least display a message advising as such esp if using the latest LCM. (surely if we’re talking about online LCM it would not be difficult to do this if a release goes EOL?)

Having to manually decide to go down the ‘old’ Upgrade Software route after everyone is told use LCM, use LCM, use LCM - is a little counter intuitive to the end user?

@Kcmount Yes, I can understand. Unfortunately, it was a design decision made to avoid suggesting an upgrade option to an AOS version that is already EOL. Nutanix ENG team is actively working on implementing INFO messages that can be shown on the LCM page to inform about AOS versions going EOL beforehand to avoid this situation. For now, LCM should still offer an upgrade option in scenarios wherein customers can upgrade from EOL AOS to a Supported AOS release version.

However, in situations like the above wherein the upgrade path is to upgrade from one EOL AOS version to the another AOS version that is also EOL, in this case, both LCM and 1-click won’t show these upgrades since the target version is EOL. In this case, the only option would be to follow the old procedure and manually upload the AOS binary and metadata files in prism to upgrade AOS in the cluster. 

Thanks for the explanation :)

I'll look forward to the updates to improve this experience as the release being EOL makes sense but as it's supported to upgrade from current point A to a supported point B (albeit via C, D) the definition of Lifecycle Management is kind of the point here :)

@cameron this might be something to think about for user experience.