[WIP] add trace logs to port-forward related code

[flavianmissi]

Pull in code from kubernetes#133775 to run it in payload tests.

[openshift-ci-robot]

@flavianmissi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• d9dc7f8|test/e2e/kubectl/portforward: print stdout and err for cmd: does not specify an upstream backport in the commit message
• f095bb5|wip: add trace calls to port-forwarding related code: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: flavianmissi
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[flavianmissi]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-sts-ovn

[openshift-ci]

@flavianmissi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-sts-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/be5061f0-84c8-11f0-8115-c7528b543b27-0

[openshift-ci-robot]

@flavianmissi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 83f0178|fix build: does not specify an upstream backport in the commit message
• d9dc7f8|test/e2e/kubectl/portforward: print stdout and err for cmd: does not specify an upstream backport in the commit message
• f095bb5|wip: add trace calls to port-forwarding related code: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[flavianmissi]

/payload-cancel

[openshift-ci]

@flavianmissi: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[flavianmissi]

/payload-abort

[openshift-ci]

@flavianmissi: aborted active payload jobs for pull request #2438

[flavianmissi]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-sts-ovn 6

[openshift-ci]

@flavianmissi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-rosa-sts-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b24318c0-84c9-11f0-950e-1134164025cd-0

[openshift-ci-robot]

@flavianmissi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 289615f|fix port-forward output parsing: does not specify an upstream backport in the commit message
• 83f0178|fix build: does not specify an upstream backport in the commit message
• d9dc7f8|test/e2e/kubectl/portforward: print stdout and err for cmd: does not specify an upstream backport in the commit message
• f095bb5|wip: add trace calls to port-forwarding related code: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@flavianmissi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 289615f|fix port-forward output parsing: does not specify an upstream backport in the commit message
• 383db43|fix code so it builds: does not specify an upstream backport in the commit message
• 83f0178|fix build: does not specify an upstream backport in the commit message
• d9dc7f8|test/e2e/kubectl/portforward: print stdout and err for cmd: does not specify an upstream backport in the commit message
• f095bb5|wip: add trace calls to port-forwarding related code: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

@flavianmissi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-runc	383db43	link	true	/test e2e-aws-ovn-runc
ci/prow/e2e-aws-crun-wasm	383db43	link	true	/test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-techpreview-serial	383db43	link	false	/test e2e-aws-ovn-techpreview-serial
ci/prow/k8s-e2e-gcp-ovn	383db43	link	true	/test k8s-e2e-gcp-ovn
ci/prow/k8s-e2e-gcp-serial	383db43	link	true	/test k8s-e2e-gcp-serial
ci/prow/verify	383db43	link	true	/test verify
ci/prow/okd-scos-e2e-aws-ovn	383db43	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp	383db43	link	true	/test e2e-gcp
ci/prow/e2e-aws-ovn-cgroupsv2	383db43	link	true	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-metal-ipi-ovn-ipv6	383db43	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-techpreview	383db43	link	false	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-fips	383db43	link	true	/test e2e-aws-ovn-fips
ci/prow/verify-commits	383db43	link	true	/test verify-commits
ci/prow/e2e-aws-ovn-crun	383db43	link	true	/test e2e-aws-ovn-crun

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.