This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 276
Collect bug report for e2e failures #4504
Merged
snehachhabria
merged 1 commit into
openservicemesh:main
from
nshankar13:collect_bug_report_e2e_failures
Feb 3, 2022
Merged
Collect bug report for e2e failures #4504
snehachhabria
merged 1 commit into
openservicemesh:main
from
nshankar13:collect_bug_report_e2e_failures
Feb 3, 2022
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
nshankar13
requested review from
draychev,
jaellio,
nojnhuh,
shashankram and
snehachhabria
as code owners
February 3, 2022 03:33
Codecov Report
@@ Coverage Diff @@
## main #4504 +/- ##
==========================================
- Coverage 69.25% 69.22% -0.03%
==========================================
Files 213 213
Lines 14625 14625
==========================================
- Hits 10128 10124 -4
- Misses 4446 4450 +4
Partials 51 51
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
nshankar13
force-pushed
the
collect_bug_report_e2e_failures
branch
from
February 3, 2022 03:49
2fee28e
to
4938246
Compare
trstringer
reviewed
Feb 3, 2022
shashankram
suggested changes
Feb 3, 2022
nshankar13
force-pushed
the
collect_bug_report_e2e_failures
branch
2 times, most recently
from
February 3, 2022 17:26
9458b79
to
a766b1f
Compare
shashankram
suggested changes
Feb 3, 2022
nshankar13
force-pushed
the
collect_bug_report_e2e_failures
branch
2 times, most recently
from
February 3, 2022 18:48
913cd0b
to
91cfcad
Compare
Signed-off-by: nshankar13 <[email protected]>
shashankram
approved these changes
Feb 3, 2022
trstringer
approved these changes
Feb 3, 2022
snehachhabria
approved these changes
Feb 3, 2022
schristoff
pushed a commit
to schristoff/osm
that referenced
this pull request
Feb 22, 2022
Signed-off-by: nshankar13 <[email protected]>
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.
Signed-off-by: nshankar13 [email protected]
Description: Use the
osm support bug-report
command to collect mesh related logs for e2e CI Failures.Testing done: Ensured that the
osm support bug-report
command was not run for successful tests. Then, I deliberately changed the test condition in one of the tests to fail, and saw that the command was run:Collecting logs, using "/home/nshankar13/documents/new_osm_fork/osm/scripts/get-osm-namespace-logs.sh /tmp/test-1376025377" Running locally '/home/nshankar13/documents/new_osm_fork/osm/scripts/get-osm-namespace-logs.sh /tmp/test-1376025377' Running locally 'kubectl get events -A' Running locally '../../bin/osm proxy get config_dump client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/config_dump.txt' Running locally '../../bin/osm proxy get clusters client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/clusters.txt' Running locally '../../bin/osm proxy get certs client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/certs.txt' Running locally '../../bin/osm proxy get listeners client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/listeners.txt' Running locally '../../bin/osm proxy get ready client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/ready.txt' Running locally '../../bin/osm proxy get stats client --namespace client -f /tmp/test-1376025377/envoy_configs/client_client/stats.txt'
Running locally '../../bin/osm support bug-report --all -o=/tmp/test-1376025377/osm_bug_report.tar.gz'
stdout:
[+] Created staging dir /tmp/osm_bug_report_805321390 to generate bug report
[+] Collecting information about meshed namespaces
✓ Finished generating report for meshed namespaces
[+] Collecting information from individual app namespaces
✓ Collected report from Namespace "client"
✓ Finished generating report for individual app namespaces
[+] Collecting information from individual app pods
✓ Collected report for Pod "client/client"
✓ Finished generating report for individual app pods
[+] Collecting information from control plane pods
✓ Collected report for Pod osm-system/osm-bootstrap-bd8d4d478-xtbng
✓ Collected report for Pod osm-system/osm-controller-844549fd77-gmzkq
✓ Collected report for Pod osm-system/osm-injector-675bd48898-9tmb2
✓ Finished generating report for control plane pods
[+] Collecting ingress information
✓ Finished generating report for ingress
[+] Collecting information from individual app namespaces
✓ Bug report successfully archived to /tmp/test-1376025377/osm_bug_report.tar.gz
Output file was successfully generated in /tmp/test-1376025377 folder:
nshankar13@DESKTOP-U63CGKH:/tmp/test-1376025377$ ls
envoy_configs events osm_bug_report.tar.gz
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project?
Is this a breaking change?
Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)?