origin
origin copied to clipboard
openshift
SPLAT-1439: Ignore edge workers when listing nodes
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}
@jcpowermac: This pull request references SPLAT-1439 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 spike to target the "4.16.0" version, but no target version was set.
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.
I'd suggest remove from the list as it seems valid for run on edge workloads:
* test/extended/kernel/common.go * test/extended/machines/workers.go * test/extended/olm/olm.go * test/extended/security/labels.go * test/extended/security/fips.goOther than that it seems to be fine, WDYT?
sgtm, updated
@jcpowermac: The following commands are available to trigger required jobs:
-
/test e2e-aws-jenkins -
/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 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback -
/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-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-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-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-e2e-gcp
Use /test all to run the following jobs that were automatically triggered:
-
pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd -
pull-ci-openshift-origin-master-e2e-aws-csi -
pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2 -
pull-ci-openshift-origin-master-e2e-aws-ovn-fips -
pull-ci-openshift-origin-master-e2e-aws-ovn-serial -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade -
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade -
pull-ci-openshift-origin-master-e2e-gcp-csi -
pull-ci-openshift-origin-master-e2e-gcp-ovn -
pull-ci-openshift-origin-master-e2e-gcp-ovn-image-ecosystem -
pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade -
pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade -
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 -
pull-ci-openshift-origin-master-e2e-metal-ipi-sdn -
pull-ci-openshift-origin-master-e2e-openstack-ovn -
pull-ci-openshift-origin-master-images -
pull-ci-openshift-origin-master-lint -
pull-ci-openshift-origin-master-unit -
pull-ci-openshift-origin-master-verify -
pull-ci-openshift-origin-master-verify-deps
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.
@jcpowermac: 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 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback -
/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-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-e2e-gcp -
/test okd-scos-images
Use /test all to run the following jobs that were automatically triggered:
-
pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd -
pull-ci-openshift-origin-master-e2e-aws-csi -
pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2 -
pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones -
pull-ci-openshift-origin-master-e2e-aws-ovn-fips -
pull-ci-openshift-origin-master-e2e-aws-ovn-serial -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial -
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade -
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade -
pull-ci-openshift-origin-master-e2e-gcp-csi -
pull-ci-openshift-origin-master-e2e-gcp-ovn -
pull-ci-openshift-origin-master-e2e-gcp-ovn-image-ecosystem -
pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade -
pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade -
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6 -
pull-ci-openshift-origin-master-e2e-metal-ipi-sdn -
pull-ci-openshift-origin-master-e2e-openstack-ovn -
pull-ci-openshift-origin-master-images -
pull-ci-openshift-origin-master-lint -
pull-ci-openshift-origin-master-unit -
pull-ci-openshift-origin-master-verify -
pull-ci-openshift-origin-master-verify-deps
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.
Job Failure Risk Analysis for sha: 1ef11b588877a46d5cad3b5d53d3143060ee3486
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade | High [sig-apps] job-upgrade This test has passed 100.00% of 88 runs on jobs ['periodic-ci-openshift-release-master-ci-4.17-e2e-aws-ovn-upgrade'] in the last 14 days. |
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jcpowermac, mtulio, neisw
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [neisw]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 5f629ff051c71eb4b08f96a68fa972bb42d56740 and 2 for PR HEAD 1ef11b588877a46d5cad3b5d53d3143060ee3486 in total
/retest-required
Remaining retests: 0 against base HEAD 49b37948e2b9507cd3fd06d9a1ccb33d45e44e3f and 1 for PR HEAD 1ef11b588877a46d5cad3b5d53d3143060ee3486 in total
@jcpowermac: 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 | 1ef11b588877a46d5cad3b5d53d3143060ee3486 | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-single-node-serial | 1ef11b588877a46d5cad3b5d53d3143060ee3486 | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-gcp-ovn-rt-upgrade | 1ef11b588877a46d5cad3b5d53d3143060ee3486 | link | false | /test e2e-gcp-ovn-rt-upgrade |
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.
/retest-required
Remaining retests: 0 against base HEAD 548b00c0cc556de873f3af2df50e2e8e280ff4b0 and 0 for PR HEAD 1ef11b588877a46d5cad3b5d53d3143060ee3486 in total
[ART PR BUILD NOTIFIER]
This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202405160942.p0.g6c5f551.assembly.stream.el9 for distgit openshift-enterprise-tests. All builds following this will include this PR.
