Skip to content

SPLAT-2642: e2e/ccm/aws/edge: skip CCM tests on unsupported scenarios#75166

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
mtulio:OCPBUGS-77166-skip-on-edge
Feb 24, 2026
Merged

SPLAT-2642: e2e/ccm/aws/edge: skip CCM tests on unsupported scenarios#75166
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
mtulio:OCPBUGS-77166-skip-on-edge

Conversation

@mtulio
Copy link
Copy Markdown
Contributor

@mtulio mtulio commented Feb 23, 2026

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 23, 2026
@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 23, 2026
@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@mtulio mtulio changed the title e2e/ccm/aws/edge: skip CCM tests on unsupported scenarios SPLAT-2642: e2e/ccm/aws/edge: skip CCM tests on unsupported scenarios Feb 23, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 23, 2026

@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.

Details

In response to this:

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

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.

@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

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
@mtulio mtulio force-pushed the OCPBUGS-77166-skip-on-edge branch from d226524 to b589a51 Compare February 23, 2026 15:49
@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

/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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@mtulio: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-5.0-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.23-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.22-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.21-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.20-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.19-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-edge-zones openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-installer-main-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.23-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.22-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.21-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.20-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.19-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.18-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.18-altinfra-e2e-aws-ovn-localzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.18-altinfra-e2e-aws-ovn-wavelengthzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.17-altinfra-e2e-aws-ovn-localzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.17-altinfra-e2e-aws-ovn-wavelengthzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.17-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.16-e2e-aws-ovn-edge-zones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.16-altinfra-e2e-aws-ovn-localzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.16-altinfra-e2e-aws-ovn-wavelengthzones openshift/installer presubmit Registry content changed
pull-ci-openshift-installer-release-4.15-altinfra-e2e-aws-ovn-localzones openshift/installer presubmit Registry content changed

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-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 23, 2026

@mtulio: The following test 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/rehearse/periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones b589a51 link unknown /pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ovn-edge-zones

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-sigs/prow repository. I understand the commands that are listed here.

@mtulio
Copy link
Copy Markdown
Contributor Author

mtulio commented Feb 23, 2026

/pj-rehearse ack

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@mtulio: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 23, 2026
@jcpowermac
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Feb 24, 2026

@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.

Details

In response to this:

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

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.

@smg247
Copy link
Copy Markdown
Member

smg247 commented Feb 24, 2026

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 24, 2026

[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

Details 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 95e6893 into openshift:main Feb 24, 2026
19 of 20 checks passed
@mtulio mtulio deleted the OCPBUGS-77166-skip-on-edge branch February 24, 2026 13:19
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 3, 2026
…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
kannon92 pushed a commit to kannon92/release that referenced this pull request Mar 3, 2026
…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
wangke19 pushed a commit to wangke19/release that referenced this pull request Mar 4, 2026
…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
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 5, 2026
…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
sdodson pushed a commit to sdodson/release that referenced this pull request Mar 8, 2026
…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
SeanZhao-redhat pushed a commit to SeanZhao-redhat/openshift-release that referenced this pull request Mar 9, 2026
…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
kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Mar 11, 2026
…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
tareqalayan pushed a commit to tareqalayan/release that referenced this pull request Mar 13, 2026
…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
qiliRedHat pushed a commit to qiliRedHat/release that referenced this pull request Mar 13, 2026
…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
MayXuQQ pushed a commit to MayXuQQ/release that referenced this pull request Mar 17, 2026
…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
kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Mar 17, 2026
…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
sairameshv pushed a commit to sairameshv/release that referenced this pull request Mar 23, 2026
…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
zhouying7780 pushed a commit to zhouying7780/release that referenced this pull request Mar 25, 2026
…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
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 25, 2026
…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
anpingli pushed a commit to anpingli/release that referenced this pull request Mar 30, 2026
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants