[wip]test zero value

[QiWang19]

- What I did

- How to verify it

- Description for the changelog

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

@QiWang19: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

• /test cluster-bootimages
• /test e2e-agnostic-upgrade
• /test e2e-aws
• /test e2e-aws-upgrade
• /test e2e-azure-upgrade
• /test e2e-gcp-op
• /test e2e-gcp-upgrade
• /test e2e-metal-ipi-ovn-ipv6
• /test e2e-ovirt-upgrade
• /test images
• /test okd-images
• /test unit
• /test verify

The following commands are available to trigger optional jobs:

• /test e2e-aws-disruptive
• /test e2e-aws-proxy
• /test e2e-aws-serial
• /test e2e-aws-single-node
• /test e2e-aws-workers-rhel7
• /test e2e-azure
• /test e2e-gcp-op-single-node
• /test e2e-gcp-single-node
• /test e2e-metal-assisted
• /test e2e-metal-ipi
• /test e2e-metal-ipi-ovn-dualstack
• /test e2e-openstack
• /test e2e-openstack-parallel
• /test e2e-ovirt
• /test e2e-ovn-step-registry
• /test e2e-vsphere
• /test e2e-vsphere-upgrade
• /test e2e-vsphere-upi
• /test okd-e2e-aws
• /test okd-e2e-gcp-op
• /test okd-e2e-upgrade
• /test okd-e2e-vsphere

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-machine-config-operator-release-4.8-e2e-agnostic-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-aws
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-aws-serial
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-aws-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-aws-workers-rhel7
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-azure-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-gcp-op
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-gcp-op-single-node
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-gcp-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-metal-assisted
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-metal-ipi
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-metal-ipi-ovn-dualstack
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-metal-ipi-ovn-ipv6
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-ovn-step-registry
• pull-ci-openshift-machine-config-operator-release-4.8-e2e-vsphere-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-images
• pull-ci-openshift-machine-config-operator-release-4.8-okd-e2e-aws
• pull-ci-openshift-machine-config-operator-release-4.8-okd-e2e-upgrade
• pull-ci-openshift-machine-config-operator-release-4.8-okd-images
• pull-ci-openshift-machine-config-operator-release-4.8-unit
• pull-ci-openshift-machine-config-operator-release-4.8-verify

Details

In response to this:

/test

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/test-infra repository.

[QiWang19]

/test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: QiWang19
Once this PR has been reviewed and has the lgtm label, please assign yuqi-zhang for approval. For more information see the Kubernetes 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

[openshift-ci]

@QiWang19: 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-metal-ipi-ovn-dualstack	6eb99cf	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-agnostic-upgrade	6eb99cf	link	true	/test e2e-agnostic-upgrade
ci/prow/e2e-metal-assisted	6eb99cf	link	false	/test e2e-metal-assisted
ci/prow/okd-e2e-aws	6eb99cf	link	false	/test okd-e2e-aws
ci/prow/e2e-vsphere-upgrade	6eb99cf	link	false	/test e2e-vsphere-upgrade
ci/prow/okd-e2e-upgrade	6eb99cf	link	false	/test okd-e2e-upgrade
ci/prow/e2e-azure-upgrade	6eb99cf	link	true	/test e2e-azure-upgrade
ci/prow/e2e-ovn-step-registry	6eb99cf	link	false	/test e2e-ovn-step-registry
ci/prow/e2e-gcp-op-single-node	6eb99cf	link	false	/test e2e-gcp-op-single-node
ci/prow/e2e-gcp-upgrade	6eb99cf	link	true	/test e2e-gcp-upgrade
ci/prow/e2e-aws	6eb99cf	link	true	/test e2e-aws

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/test-infra 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