-
Notifications
You must be signed in to change notification settings - Fork 42
[minor] Support for Manage Foundation installation during an upgrade from MAS 9.0 without Manage to MAS 9.1 #1570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
…oundation installation.
…age Foundation installation would work in the upgrade pipeline.
Adding a silent mode in configDb2 so that we don't bother the user with DB2 settings when Manage Foundation needs to be installed.
…eraction. For MAS installation, only set configDB2 to silent mode if IoT is not going to be installed and Manage Foundation is going to be installed.
…ble for installing Manage Foundation, to make sure they don't run when they are not supposed to.
…tChannel to be set manually in dev mode.
…tials to the Manage Foundation so that these prompts are not requested in scenarios where Manage Foundation would not be installed.
… it to launchUpgradePipeline because it looks like that nextChannel is only informative. The actual channel to be upgraded to is derived from a compatibility matrix in ansible-devops.
…dd an extra when clause to Manage Foundation tasks hoping that they will not overwrite the ones in the template.
…when clause is appended to existing entries, while still keeping indentation correct.
… in the upgrade_path.
…y installed db2-system will be already installed.
…use the 9.1.x-dev channel.
…ing Manage Foundation.
…ops for some more testing.
alequint
previously approved these changes
Apr 29, 2025
alequint
approved these changes
May 6, 2025
Contributor
|
Looks good to me! |
Contributor
|
Just changed PR title to include |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes in this PR:
mas upgradecommand will now install Manage Foundation. Added DB2 and Manage installation tekton tasks inupgrade.yml.j2for this specific scenario.mas_app_settings_aio_flagparam to false (both install and upgrade scenarios).--dev-modetomas upgradeso that the upgrade channel for Manage Foundation installation can be entered manually during tests. Artifactory username and token are also requested in dev mode.Tested the following scenarios: