CASM-4467 stable 1.5 #2580
Merged
CASM-4467 stable 1.5 #2580
Conversation
This file contains 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
dzou-hpe
approved these changes
Jul 19, 2023
This was referenced Jul 19, 2023
|
/backport release/1.5 |
|
Backporting into branch release/1.5 was successful. New PR: #2592 |
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.
Summary and Scope
Cray-cli recently introduced a
-tenantoption as part ofcray initcommand. When it was introduced, thistenantflag was required. However, this caused issues with existing scripts as none of them supplied the-tenantflag.The
-tenantflag was then made optional. However, the iuf-container image still used the version of cray-cli where the-tenantflag was required. This is causing issues indeliver-productanddeploy-productstages.Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Yes
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
Tested on:
Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?
Ran IUF
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
No
Pull Request Checklist