origin
origin copied to clipboard
openshift
[release-4.16] OCPBUGS-38707: run vsphere driver config test on non techpreview clusters
This is an automated cherry-pick of #28848
/assign RomanBednar
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: STOR-1839
In response to this:
This is an automated cherry-pick of #28848
/assign RomanBednar
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 openshift-eng/jira-lifecycle-plugin repository.
@openshift-cherrypick-robot: 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-single-node-upgrade | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-vsphere-ovn-dualstack-primaryv6 |
| ci/prow/e2e-azure-ovn-upgrade | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-azure-ovn-upgrade |
| ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-metal-ipi-ovn-dualstack-local-gateway |
| ci/prow/e2e-aws-ovn-ipsec-serial | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-aws-ovn-ipsec-serial |
| ci/prow/e2e-aws-ovn-single-node-serial | d5f97efc43339430b71c17d76d996fbd7172b2fc | link | false | /test e2e-aws-ovn-single-node-serial |
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-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@jsafrane: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:
/test e2e-aws-jenkins/test e2e-aws-ovn-edge-zones/test e2e-aws-ovn-fips/test e2e-aws-ovn-image-registry/test e2e-aws-ovn-serial/test e2e-gcp-ovn/test e2e-gcp-ovn-builds/test e2e-gcp-ovn-image-ecosystem/test e2e-gcp-ovn-upgrade/test e2e-metal-ipi-ovn-ipv6/test images/test lint/test unit/test verify/test verify-deps
The following commands are available to trigger optional jobs:
/test e2e-agnostic-ovn-cmd/test e2e-aws/test e2e-aws-csi/test e2e-aws-disruptive/test e2e-aws-etcd-recovery/test e2e-aws-multitenant/test e2e-aws-ovn/test e2e-aws-ovn-cgroupsv2/test e2e-aws-ovn-etcd-scaling/test e2e-aws-ovn-ipsec-serial/test e2e-aws-ovn-kubevirt/test e2e-aws-ovn-single-node/test e2e-aws-ovn-single-node-serial/test e2e-aws-ovn-single-node-upgrade/test e2e-aws-ovn-upgrade/test e2e-aws-ovn-upi/test e2e-aws-proxy/test e2e-azure/test e2e-azure-ovn-etcd-scaling/test e2e-azure-ovn-upgrade/test e2e-baremetalds-kubevirt/test e2e-gcp-csi/test e2e-gcp-disruptive/test e2e-gcp-fips-serial/test e2e-gcp-ovn-etcd-scaling/test e2e-gcp-ovn-rt-upgrade/test e2e-gcp-ovn-techpreview/test e2e-gcp-ovn-techpreview-serial/test e2e-metal-ipi-ovn-dualstack/test e2e-metal-ipi-ovn-dualstack-local-gateway/test e2e-metal-ipi-sdn/test e2e-metal-ipi-serial/test e2e-metal-ipi-serial-ovn-ipv6/test e2e-metal-ipi-virtualmedia/test e2e-openstack-ovn/test e2e-openstack-serial/test e2e-vsphere/test e2e-vsphere-ovn-dualstack-primaryv6/test e2e-vsphere-ovn-etcd-scaling/test okd-scos-images
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-origin-release-4.16-e2e-agnostic-ovn-cmdpull-ci-openshift-origin-release-4.16-e2e-aws-csipull-ci-openshift-origin-release-4.16-e2e-aws-ovn-cgroupsv2pull-ci-openshift-origin-release-4.16-e2e-aws-ovn-edge-zonespull-ci-openshift-origin-release-4.16-e2e-aws-ovn-fipspull-ci-openshift-origin-release-4.16-e2e-aws-ovn-ipsec-serialpull-ci-openshift-origin-release-4.16-e2e-aws-ovn-serialpull-ci-openshift-origin-release-4.16-e2e-aws-ovn-single-nodepull-ci-openshift-origin-release-4.16-e2e-aws-ovn-single-node-serialpull-ci-openshift-origin-release-4.16-e2e-aws-ovn-single-node-upgradepull-ci-openshift-origin-release-4.16-e2e-aws-ovn-upgradepull-ci-openshift-origin-release-4.16-e2e-azure-ovn-upgradepull-ci-openshift-origin-release-4.16-e2e-gcp-csipull-ci-openshift-origin-release-4.16-e2e-gcp-ovnpull-ci-openshift-origin-release-4.16-e2e-gcp-ovn-rt-upgradepull-ci-openshift-origin-release-4.16-e2e-gcp-ovn-upgradepull-ci-openshift-origin-release-4.16-e2e-metal-ipi-ovn-dualstack-local-gatewaypull-ci-openshift-origin-release-4.16-e2e-metal-ipi-ovn-ipv6pull-ci-openshift-origin-release-4.16-e2e-metal-ipi-sdnpull-ci-openshift-origin-release-4.16-e2e-openstack-ovnpull-ci-openshift-origin-release-4.16-e2e-vsphere-ovn-dualstack-primaryv6pull-ci-openshift-origin-release-4.16-imagespull-ci-openshift-origin-release-4.16-lintpull-ci-openshift-origin-release-4.16-unitpull-ci-openshift-origin-release-4.16-verifypull-ci-openshift-origin-release-4.16-verify-deps
In response to this:
/test help looking for a vsphere job
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.
/approve
waiting for green CI with successful [sig-storage][Feature:VSphereDriverConfiguration][Serial][apigroup:operator.openshift.io] vSphere CSI Driver Configuration
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-serial
@jsafrane: 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.18-e2e-vsphere-ovn-serial
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fad39f40-5b32-11ef-801b-1393fbb16c86-0
@jsafrane: 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.
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-serial
@jsafrane: 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.
@jsafrane: 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.18-e2e-vsphere-ovn-serial
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1033e1b0-5b33-11ef-89a0-342bd0c83c40-0
/payload-job periodic-ci-openshift-release-master-nightly-4.16-e2e-vsphere-ovn-serial
@jsafrane: 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.16-e2e-vsphere-ovn-serial
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2359c480-5b33-11ef-8449-6198b83016e1-0
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jsafrane, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~test/extended/storage/OWNERS~~ [jsafrane]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@RomanBednar: This pull request references STOR-1839 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.z" version, but no target version was set.
In response to this:
/jira refresh
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 openshift-eng/jira-lifecycle-plugin repository.
/retitle [release-4.16] OCPBUGS-38707: run vsphere driver config test on non techpreview clusters
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-38707, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
- expected Jira Issue OCPBUGS-38707 to depend on a bug targeting a version in 4.17.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #28848
/assign RomanBednar
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 openshift-eng/jira-lifecycle-plugin repository.
@RomanBednar: This pull request references Jira Issue OCPBUGS-38707, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
- expected Jira Issue OCPBUGS-38707 to depend on a bug targeting a version in 4.17.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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 openshift-eng/jira-lifecycle-plugin repository.
@RomanBednar: This pull request references Jira Issue OCPBUGS-38707, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.16.z) matches configured target version for branch (4.16.z)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-38710 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-38710 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
- bug has dependents
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.
In response to this:
/jira refresh
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 openshift-eng/jira-lifecycle-plugin repository.
@Phaow: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]
In response to this:
/label cherry-pick-approved
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.