CASMTRIAGE-6953: IMS import tool: More accurately determine IMS data file paths #5373
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
|
/backport release/1.5 release/1.4 release/1.3 |
|
Backporting into branch release/1.5 was successful. New PR: #5374 |
|
Backporting into branch release/1.4 was successful. New PR: #5375 |
|
Backporting into branch release/1.3 was successful. New PR: #5376 |
mharding-hpe
requested review from
rustydb,
mbuchmann-hpe,
dlaine-hpe,
kimjensen-hpe and
leliasen-hpe
rustydb
approved these changes
Sep 13, 2024
mharding-hpe
force-pushed
the
CASMTRIAGE-6953
branch
from
c29cdcb
to
3a26229
Compare
rustydb
approved these changes
Sep 13, 2024
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.
The IMS import tool currently assumes that for any given type of IMS data (images, deleted recipes, etc), there will be only a single data file in
/var/ims/datain the IMS pod. However, this is not always the case.This PR modifies the importer to be smarter. It looks at the IMS server source code inside the IMS pod to determine the correct data file to update. This prevents failures like the ones reported in CASMTRIAGE-6953, where the import tool is confused when there are multiple choices.
Backports:
No earlier backports needed, as this tool did not exist prior to CSM 1.3