SPLAT-2642: e2e/ccm/aws/edge: skip CCM tests on unsupported scenarios#75166
Conversation
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@mtulio: This pull request references SPLAT-2642 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 task to target the "4.22.0" version, but no target version was set. DetailsIn 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 can see BYO VPC jobs failing too, let me add exception for those in the workflow level: |
Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
d226524 to
b589a51
Compare
|
/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones pull-ci-openshift-installer-main-e2e-aws-ovn-shared-vpc-edge-zones |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 77 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
BYO vpc is about to fail when install, running periodic instead presubmit: /pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-shared-vpc-edge-zones |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@mtulio: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/pj-rehearse ack |
|
@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/lgtm |
|
@mtulio: This pull request references SPLAT-2642 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 task to target the "4.22.0" version, but no target version was set. DetailsIn 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcpowermac, mtulio, smg247 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
95e6893
into
openshift:main
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
…75166) Skip e2e tests scheduled in unsupported scenarios of edge zones. Edge zones requires tolerations to satisfy the unscheduled nodes by design. We need to skip the test while fixes isnt delivered in upstream. References: https://issues.redhat.com/browse/OCPBUGS-77166 `https://github.com/kubernetes/cloud-provider-aws/pull/1340` aws/edge: run edge zone jobs twice a week Edge zone jobs eventually blocks critical projects, such as origin, installer, etc without proper monitoring. We are moving from weekly to twice a week job run on mainstream to get more visibiility of existing issues. Currently job failures notifications are sent to the channel #forum-ocp-splat-alerts on Slack (which is also quite busy). aws/edge/byo-vpc: extend the skips to the BYO scenarios
Skip CCM AWS e2e tests scheduled in unsupported scenarios of edge zones.
Edge zones requires tolerations to satisfy the unscheduled nodes by design.
We need to skip the test while fixes isnt delivered in upstream.
References:
https://issues.redhat.com/browse/OCPBUGS-77166
https://github.com/kubernetes/cloud-provider-aws/pull/1340