[patch] add cpd 5.3.1 to upgrade path to allow update when already at target version - #2602
Merged
Merged
Conversation
… 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
anilprajapatiibm
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CP4D 5.3.1 was not present as a key in cpdUpgradePath, causing
mas updateto 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