When attempting to perform a Network Function (NF) upgrade in TCA, the expected version of the onboarded CSAR package does not appear in the selection menu, even though:
2.x, 3.x
This issue occurs because of a Product Name or vnfdId mismatch between the currently instantiated NF and the new CSAR package.
In TCA and ETSI SOL001 standards, the vnfdId (or product_name) serves as the unique identifier for a functional product. TCA filters the upgrade list to only display packages that share the exact same vnfdId (or product_name) as the instance being upgraded.
If the existing instance (e.g., v1.3) uses Product-A and the new package (e.g., v1.4) uses Product-B (or a modified ID like Product-A-1.4), TCA treats them as entirely different products rather than sequential versions of the same product. Consequently, the new version is excluded from the upgrade path.
To resolve this issue, ensure that the vnfdId in the new CSAR package exactly matches the vnfdId of the currently instantiated NF.
vnfdId or product_name.vnfdId in the v1.4 package to match the v1.3 package exactly.