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
Bug 1877428: Update gather_core_dumps to get raw coredump files #173
Bug 1877428: Update gather_core_dumps to get raw coredump files #173
Conversation
2d1f234
to
ed33dca
Compare
/retest |
1 similar comment
/retest |
ed33dca
to
822d9c5
Compare
/retest |
822d9c5
to
541f4c9
Compare
/assign @RickJWagner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
The previous iteration of `gather_core_dumps` used `coredumpsctl info` to get information It was shown that we in fact need the raw coredump files for debugging This PR extracts corefiles from the nodes by 1. Forcing a Debug pod to stay open on node 2. Waiting for the Debug pod to run 3. Using `oc cp` to extract the necessary files It does the node dump collection in parallel to increase efficiency TODO: find a way to do this without forcing the debug pod to stay running Add parellel running method to other network log collection scripts Signed-off-by: Andrew Stoycos <astoycos@redhat.com>
541f4c9
to
b72263f
Compare
@rbbratta should be all good now |
/lgtm |
/lgtm |
@astoycos: This pull request references Bugzilla bug 1877428, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@astoycos: This pull request references Bugzilla bug 1877428, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@JacobTanenbaum: This pull request references Bugzilla bug 1877428, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astoycos, davemulford, trozet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@astoycos: All pull requests linked via external trackers have merged: Bugzilla bug 1877428 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
in response to the [feedback from QA](https://bugzilla.redhat.com/show_bug.cgi?id=1877428) It updated how the name of the debug pod is determined Specifically it uses `sed` to extract the pod name when the pod is created with `oc debug`
in response to the [feedback from QA](https://bugzilla.redhat.com/show_bug.cgi?id=1877428) It updated how the name of the debug pod is determined Specifically it uses `sed` to extract the pod name when the pod is created with `oc debug` Signed-off-by: Andrew Stoycos <astoycos@redhat.com>
in response to the [feedback from QA](https://bugzilla.redhat.com/show_bug.cgi?id=1877428) It updated how the name of the debug pod is determined Specifically it uses `sed` to extract the pod name when the pod is created with `oc debug` Signed-off-by: Andrew Stoycos <astoycos@redhat.com>
in response to the [feedback from QA](https://bugzilla.redhat.com/show_bug.cgi?id=1877428) It updated how the name of the debug pod is determined Specifically it uses `sed` to extract the pod name when the pod is created with `oc debug` Signed-off-by: Andrew Stoycos <astoycos@redhat.com>
The previous iteration of
gather_core_dumps
usedcoredumpsctl info
to get informationIt was shown that we in fact need the raw coredump
files for debugging
This PR extracts corefiles from the nodes by
oc cp
to extract the necessary filesTODO: find a way to do this without forcing the
debug pod to stay running
Signed-off-by: Andrew Stoycos astoycos@redhat.com