This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
EOS-27405: Update log collector to use correct pod names #51
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
Fix pod names and add additional ones. Fixed an unrelated issue where logs where truncated due to a bad printf format string. Add log tar file to gitignore. Signed-off-by: Keith Pine <[email protected]>
|
Created https://jts.seagate.com/browse/EOS-27546 for the default container issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
cortx-controlandcortx-datapod names changed, so the log collector script has been updated to reflect that.Added additional pods to collect from,
cortx-haandcortx-server.I found an unrelated issue where the CSM agent container logs had an error string that caused a bash
printfto truncate the logs.Another issue that I saw (not addressed in this PR) is that the CORTX support bundle generate is not specifying a container to run on, so k8s is picking the first container. This should be followed up to either select a default container to run the bundle on, or determine whether bundles should be generated for each container individually.
Signed-off-by: Keith Pine [email protected]