From 364259c5d5c436ab1f109f8590bdcb0b164f3848 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Sun, 20 Sep 2026 23:33:50 +0530 Subject: [PATCH] [patch] add cpd 5.3.1 to upgrade path to allow update when already at target version CP4D 5.3.1 was not present as a key in cpdUpgradePath, causing `mas update` to fatal-error with "Skipping intermediate Cloud Pak for Data updates is not tested and thus not supported" when CP4D 5.3.1 was already installed and the catalog target version was also 5.3.1. Adding "5.3.1": "5.3.1" as a self-referential entry means the version is recognised as a known leaf node. The existing elif check (cpdUpgradePath[v] != cpdTargetVersion) then evaluates "5.3.1" != "5.3.1" as False, allowing execution to fall through to the already-at-target-version path. Fixes: update pipeline not starting after install when CP4D 5.3.1 is present --- python/src/mas/cli/update/app.py | 1 + 1 file changed, 1 insertion(+) diff --git a/python/src/mas/cli/update/app.py b/python/src/mas/cli/update/app.py index 1826847ff8..4b84949b1d 100644 --- a/python/src/mas/cli/update/app.py +++ b/python/src/mas/cli/update/app.py @@ -712,6 +712,7 @@ def detectCP4D(self) -> None: return elif len(cpds) == 1: cpdUpgradePath = { + "5.3.1": "5.3.1", "5.2.0": "5.3.1", "5.1.3": "5.2.0", "5.0.0": "5.1.3",