origin
origin copied to clipboard
Published
20 hours ago •
openshift
openshift
OPRUN-3768: Add OLMv1 Single/OwnNamespace tests
@thetechnick: This pull request references OPRUN-3768 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 either version "4.20." or "openshift-4.20.", but it targets "4.19" instead.
In response to this:
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.
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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: thetechnick Once this PR has been reviewed and has the lgtm label, please assign neisw 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:
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Job Failure Risk Analysis for sha: fcc532e47193c92c5a34dcc06f84198edfb901a0
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback | High operator conditions network This test has passed 99.41% of 3884 runs on release 4.20 [Overall] in the last week. |
| pull-ci-openshift-origin-main-e2e-aws-disruptive | Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis |
| pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling | Low [bz-kube-storage-version-migrator] clusteroperator/kube-storage-version-migrator should not change condition/Available This test has passed 50.00% of 2 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week. |
| pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling | Low [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week. |
| pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling | High [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info This test has passed 99.95% of 5536 runs on release 4.20 [Overall] in the last week. |
| pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling | Medium [sig-api-machinery] disruption/oauth-api apiserver/oauth-apiserver connection/new should be available throughout the test Potential external regression detected for High Risk Test analysis --- [sig-api-machinery] disruption/openshift-api apiserver/openshift-apiserver connection/new should be available throughout the test Potential external regression detected for High Risk Test analysis --- [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis --- [sig-api-machinery] disruption/kube-api apiserver/kube-apiserver connection/new should be available throughout the test Potential external regression detected for High Risk Test analysis --- Showing 4 of 5 test results |
![openshift-trt[bot] avatar](https://avatars.githubusercontent.com/u/111778100?v=4 "Published by a pub.dev verified publisher"){kind=small}
@thetechnick: 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-serial-ovn-ipv6 | fcc532e47193c92c5a34dcc06f84198edfb901a0 | link | false | /test e2e-metal-ipi-serial-ovn-ipv6 |
| ci/prow/e2e-metal-ipi-serial | fcc532e47193c92c5a34dcc06f84198edfb901a0 | link | false | /test e2e-metal-ipi-serial |
| ci/prow/e2e-aws-ovn-serial-publicnet | fcc532e47193c92c5a34dcc06f84198edfb901a0 | link | false | /test e2e-aws-ovn-serial-publicnet |
| ci/prow/e2e-gcp-fips-serial | fcc532e47193c92c5a34dcc06f84198edfb901a0 | link | false | /test e2e-gcp-fips-serial |
| ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview |
| ci/prow/e2e-gcp-disruptive | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-gcp-disruptive |
| ci/prow/e2e-aws-ovn-single-node-serial | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-gcp-fips-serial-2of2 | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-gcp-fips-serial-2of2 |
| ci/prow/e2e-openstack-serial | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-openstack-serial |
| ci/prow/e2e-aws-ovn-serial-publicnet-1of2 | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-aws-ovn-serial-publicnet-1of2 |
| ci/prow/e2e-aws-ovn-etcd-scaling | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-aws-ovn-etcd-scaling |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-vsphere-ovn-dualstack-primaryv6 |
| ci/prow/e2e-azure-ovn-upgrade | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-azure-ovn-upgrade |
| ci/prow/e2e-azure | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-azure |
| ci/prow/e2e-metal-ipi-virtualmedia | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-metal-ipi-virtualmedia |
| ci/prow/e2e-gcp-ovn-etcd-scaling | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-gcp-ovn-etcd-scaling |
| ci/prow/e2e-aws-disruptive | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-aws-disruptive |
| ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback |
| ci/prow/e2e-vsphere-ovn-etcd-scaling | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-vsphere-ovn-etcd-scaling |
| ci/prow/okd-e2e-gcp | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test okd-e2e-gcp |
| ci/prow/e2e-gcp-fips-serial-1of2 | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-gcp-fips-serial-1of2 |
| ci/prow/okd-scos-e2e-aws-ovn | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test okd-scos-e2e-aws-ovn |
| ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-metal-ipi-ovn-kube-apiserver-rollout |
| ci/prow/e2e-azure-ovn-etcd-scaling | 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31 | link | false | /test e2e-azure-ovn-etcd-scaling |
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.
Job Failure Risk Analysis for sha: 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-main-e2e-aws-disruptive | Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis |
| pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling | Low [bz-kube-storage-version-migrator] clusteroperator/kube-storage-version-migrator should not change condition/Available This test has passed 50.00% of 2 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week. --- [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 50.00% of 2 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week. |
| pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade | IncompleteTests Tests for this run (2085) are below the historical average (4166): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
| pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling | Low [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week. |
| pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade | IncompleteTests Tests for this run (2125) are below the historical average (3058): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems) |
| pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling | High [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info This test has passed 99.94% of 5176 runs on release 4.20 [Overall] in the last week. --- [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times This test has passed 99.98% of 5176 runs on release 4.20 [Overall] in the last week. |
Risk analysis has seen new tests most likely introduced by this PR. Please ensure that new tests meet guidelines for naming and stability.
New Test Risks for sha: 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31
| Job Name | New Test Risk |
|---|---|
| pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-bgp-techpreview | High - "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator single/own namespace support should install a cluster extension in OtherNamespace mode [Suite:openshift/conformance/parallel]" is a new test, was only seen in one job, and failed 1 time(s) against the current commit. |
| pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-bgp-techpreview | High - "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator single/own namespace support should install a cluster extension in SingleNamespace mode [Suite:openshift/conformance/parallel]" is a new test, was only seen in one job, and failed 1 time(s) against the current commit. |
New tests seen in this PR at sha: 32f7d4c2e8f5b0a260625c3672e7e2304bdfed31
- "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator single/own namespace support should install a cluster extension in OtherNamespace mode [Suite:openshift/conformance/parallel]" [Total: 1, Pass: 0, Fail: 1, Flake: 0]
- "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator single/own namespace support should install a cluster extension in SingleNamespace mode [Suite:openshift/conformance/parallel]" [Total: 1, Pass: 0, Fail: 1, Flake: 0]
@perdasilva: 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-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/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 e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test images
/test lint
/test okd-scos-images
/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-certrotation
/test e2e-aws-etcd-recovery
/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-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-publicnet-1of2
/test e2e-aws-ovn-serial-publicnet-2of2
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/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-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-csi
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial-1of2
/test e2e-gcp-fips-serial-2of2
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial-1of2
/test e2e-gcp-ovn-techpreview-serial-2of2
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-bgp-virt-dualstack
/test e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial-1of2
/test e2e-metal-ipi-serial-2of2
/test e2e-metal-ipi-serial-ovn-ipv6-1of2
/test e2e-metal-ipi-serial-ovn-ipv6-2of2
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-e2e-gcp
/test okd-scos-e2e-aws-ovn
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-origin-main-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-main-e2e-aws
pull-ci-openshift-origin-main-e2e-aws-csi
pull-ci-openshift-origin-main-e2e-aws-disruptive
pull-ci-openshift-origin-main-e2e-aws-ovn
pull-ci-openshift-origin-main-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-main-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-aws-ovn-fips
pull-ci-openshift-origin-main-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-2of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-publicnet-1of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-publicnet-2of2
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-main-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-main-e2e-aws-proxy
pull-ci-openshift-origin-main-e2e-azure
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade
pull-ci-openshift-origin-main-e2e-gcp-csi
pull-ci-openshift-origin-main-e2e-gcp-disruptive
pull-ci-openshift-origin-main-e2e-gcp-fips-serial-1of2
pull-ci-openshift-origin-main-e2e-gcp-fips-serial-2of2
pull-ci-openshift-origin-main-e2e-gcp-ovn
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-main-e2e-hypershift-conformance
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-local-gateway
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-1of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-2of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-1of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-2of2
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-origin-main-e2e-openstack-ovn
pull-ci-openshift-origin-main-e2e-openstack-serial
pull-ci-openshift-origin-main-e2e-vsphere-ovn
pull-ci-openshift-origin-main-e2e-vsphere-ovn-dualstack-primaryv6
pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-e2e-gcp
pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-main-okd-scos-images
pull-ci-openshift-origin-main-unit
pull-ci-openshift-origin-main-verify
pull-ci-openshift-origin-main-verify-deps
In response to this:
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
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.
@anik120: Closed this PR.
In response to this:
/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.