Skip to content

Conversation

@djoshy
Copy link
Contributor

@djoshy djoshy commented Dec 18, 2025

This drops the 4.21 & 4.20 TechPreview periodics to once a week, removes the 4.19 TP periodics and also shards the azure default suite since it is on the edge of the 4h timeout.

@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request explicitly references no jira issue.

Details

In response to this:

This drops the 4.21 TechPreview periodics to once a week, and also shards the azure default suite since it is on the edge of the 4h timeout.

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-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2025
@yuqi-zhang
Copy link
Contributor

/hold

David plans to add 4.20 changes as well, let's do that together

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 18, 2025
@djoshy djoshy force-pushed the 4.22-branch-updates branch from f293cf3 to 58a3b67 Compare December 19, 2025 15:05
@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request explicitly references no jira issue.

Details

In response to this:

This drops the 4.21 & 4.20 TechPreview periodics to once a week, removes the 4.19 TP periodics and also shards the azure default suite since it is on the edge of the 4h timeout.

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.

@djoshy djoshy force-pushed the 4.22-branch-updates branch from 58a3b67 to 9ed0814 Compare December 19, 2025 15:16
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Should hopefully save us some resources. The only caveat here is that maybe some of our features backported to 4.21 will want some TP tests, but we should not be looking to z-stream GA anything, and we should generally be testing in 4.22, so I think this is fine to land.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 19, 2025
@djoshy djoshy force-pushed the 4.22-branch-updates branch from 9ed0814 to e3a40af Compare January 2, 2026 15:20
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 2, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@djoshy: 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
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-ipv6-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-azure-mco-disruptive-1of2 N/A periodic Periodic changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-azure-mco-disruptive-2of2 N/A periodic Periodic changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-azure-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-vsphere-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-vsphere-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-gcp-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-metal-ipi-ovn-ipv4-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-aws-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.22-periodics-e2e-azure-mco-disruptive-2of2 N/A periodic Periodic changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-ipv4-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-metal-ipi-ovn-dualstack-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-aws-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-ipv4-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-azure-mco-disruptive-1of2 N/A periodic Periodic changed
periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-metal-ipi-ovn-ipv6-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-azure-mco-disruptive N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-metal-ipi-ovn-ipv6-mco-disruptive-techpreview N/A periodic Ci-operator config changed
periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-gcp-mco-disruptive N/A periodic Ci-operator config changed
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.

@djoshy
Copy link
Contributor Author

djoshy commented Jan 2, 2026

/pj-rehearse skip

These are only interval and sharding changes, tests aren't changing functionally

@openshift-ci-robot
Copy link
Contributor

@djoshy: 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 Jan 2, 2026
@yuqi-zhang
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 2, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, yuqi-zhang

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
Copy link
Contributor

openshift-ci bot commented Jan 2, 2026

@djoshy: all tests passed!

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.

@djoshy
Copy link
Contributor Author

djoshy commented Jan 2, 2026

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 2, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 70ced34 into openshift:master Jan 2, 2026
15 checks passed
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.

3 participants