[DNM] Dummy PR to test `e2e-aws-ovn-edge-zones`

[tssurya]

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tssurya Once this PR has been reviewed and has the lgtm label, please assign xueqzhan 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:

• OWNERS

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

[openshift-ci[bot]]

@tssurya: 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-serial-2of2	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	true	/test e2e-aws-ovn-serial-2of2
ci/prow/verify-deps	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	true	/test verify-deps
ci/prow/e2e-aws-ovn-single-node	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	false	/test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-upgrade	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	535dfeb66f41fbd6f1d0d396c80ed86df94dcdea	link	false	/test e2e-aws-ovn-kube-apiserver-rollout

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.

[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-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[bot]]

@openshift-bot: Closed this PR.

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.