print the error result from UDN test failure #29370
Conversation
currently we do not print out the result if the connection does not isolate traffic for UDN tests. This does not show us what the pod is connecting to and as such don't know if there are artifacts of the old pods around or if the traffic is not isolated. Print out the result of the query so that we have more insight as to how the test failed. Signed-off-by: Jacob Tanenbaum <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: JacobTanenbaum The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-techpreview |
|
@JacobTanenbaum: trigger 4 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8a39c6f0-b8ad-11ef-8299-f358e68ca9a2-0 |
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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-sigs/prow repository. |
|
@JacobTanenbaum: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
currently we do not print out the result if the connection does not isolate traffic for UDN tests. This does not show us what the pod is connecting to and as such don't know if there are artifacts of the old pods around or if the traffic is not isolated.
Print out the result of the query so that we have more insight as to how the test failed.