WIP: write to nodeLogs instead of e2e logs

[rphillips]

No description provided.

[rphillips]

/payload help

[openshift-ci]

@rphillips: 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[rphillips]

/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ipi-ovn-runc

[openshift-ci]

@rphillips: 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.19-e2e-vsphere-ipi-ovn-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1d0363a0-0b61-11f0-9f8e-f6a0f6142aa7-0

[rphillips]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ipi-ovn-runc 3

[openshift-ci]

@rphillips: 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.19-e2e-vsphere-ipi-ovn-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/50653a70-0b61-11f0-86c9-5fb01f7e10ea-0

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-ci]

@rphillips: 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-vsphere-ovn-etcd-scaling	9b8d4e1	link	false	/test e2e-vsphere-ovn-etcd-scaling
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	9b8d4e1	link	false	/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn-single-node-upgrade	9b8d4e1	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/okd-e2e-gcp	9b8d4e1	link	false	/test okd-e2e-gcp
ci/prow/e2e-hypershift-conformance	9b8d4e1	link	false	/test e2e-hypershift-conformance
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	9b8d4e1	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-proxy	9b8d4e1	link	false	/test e2e-aws-proxy
ci/prow/e2e-azure-ovn-upgrade	9b8d4e1	link	false	/test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-ovn-etcd-scaling	9b8d4e1	link	false	/test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial	9b8d4e1	link	false	/test e2e-gcp-fips-serial
ci/prow/e2e-aws-disruptive	9b8d4e1	link	false	/test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	9b8d4e1	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-etcd-scaling	9b8d4e1	link	false	/test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-azure-ovn-etcd-scaling	9b8d4e1	link	false	/test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive	9b8d4e1	link	false	/test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-serial-1of2	9b8d4e1	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-serial	9b8d4e1	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-serial-publicnet	9b8d4e1	link	true	/test e2e-aws-ovn-serial-publicnet
ci/prow/e2e-gcp-csi	9b8d4e1	link	true	/test e2e-gcp-csi
ci/prow/e2e-aws-csi	9b8d4e1	link	true	/test e2e-aws-csi
ci/prow/go-verify-deps	9b8d4e1	link	true	/test go-verify-deps
ci/prow/e2e-aws-ovn-microshift	9b8d4e1	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-ipv6	9b8d4e1	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Details

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.

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.