Untar logs for OCP openstack pods #1941
Closed
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.
When running openstack-must-gather tool we are instructing the tool not to untar the whole SOS reports, as they contain way too may files and the file count affects zuul jobs (makes them crash).
This has created a situation where we all need to download and untar files to be able to see the container logs making it harder to have quick looks at logs and sharing URLs to have discussions.
This patch forces the untar of just the logs of the OCP cluster SOS reports. Specifically just the openstack and openstack-operators namespaces, which are the most commonly required.
Additional namespaces can be added to the
include
or we could just remove it altogether to get all pods.We are using
sosreport-*-UntarWithArg-i.tar.xz
instead of*.tar.xz
so we don't create empty directories for the EDPM nodes.Related PR: openstack-k8s-operators/openstack-must-gather#62
As a pull request owner and reviewers, I checked that: