OCPBUGS-77560: Disable non-azure permafailing hypershift-kubevirt jobs#79396
OCPBUGS-77560: Disable non-azure permafailing hypershift-kubevirt jobs#79396orenc1 wants to merge 1 commit into
Conversation
openshift-ci-robot
added
jira/valid-reference
|
@orenc1: This pull request references Jira Issue OCPBUGS-77560, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (2)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughThis pull request consolidates the periodic test schedules for three KubeVirt OVN-related test jobs across four OpenShift HyperShift release branch configurations. All targeted tests now execute on a unified cron schedule of ChangesKubeVirt Periodic Test Schedule Consolidation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
These kubevirt CI jobs have had 0% pass rate for months, wasting CI resources. Set them to run once a year instead of removing them entirely. Jobs affected: release-4.19: - periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-kubevirt-aws-ovn - periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-kubevirt-metal-ovn - periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-kubevirt-metal-ovn-disconnected release-4.20: - periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-kubevirt-aws-ovn - periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-kubevirt-metal-ovn - periodic-ci-openshift-hypershift-release-4.20-periodics-e2e-kubevirt-metal-ovn-disconnected release-4.21: - periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-kubevirt-aws-ovn - periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-kubevirt-metal-ovn - periodic-ci-openshift-hypershift-release-4.21-periodics-e2e-kubevirt-metal-ovn-disconnected release-4.22: - periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-kubevirt-aws-ovn Signed-off-by: Oren Cohen <ocohen@redhat.com> Assisted-by: Claude <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: orenc1 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
orenc1
force-pushed
the
diabled_hypershift_permafailing_jobs
branch
from
9f04820 to
3e1c8ca
Compare
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@orenc1: This pull request references Jira Issue OCPBUGS-77560, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (yli2@redhat.com), skipping review request. 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. |
|
@orenc1: all tests passed! 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. |
jparrill
left a comment
jparrill
left a comment
There was a problem hiding this comment.
Dropped a couple of questions. Thanks!
| capabilities: | ||
| - intranet | ||
| cron: 31 0 * * 0 | ||
| cron: 0 0 17 5 * |
There was a problem hiding this comment.
All 10 jobs share the same cron (0 0 17 5 *), so they'll all fire at midnight on May 17 simultaneously. That could overload the CI nodes, especially the metal jobs on equinix-ocp-hcp. Could we spread them across different hours to avoid the spike?
| workflow: hypershift-kubevirt-azure-conformance | ||
| - as: e2e-kubevirt-aws-ovn | ||
| cron: 0 0,6,12,18 * * * | ||
| cron: 0 0 17 5 * |
There was a problem hiding this comment.
The same kubevirt jobs (e2e-kubevirt-aws-ovn, e2e-kubevirt-metal-ovn, e2e-kubevirt-metal-ovn-disconnected) are still running on active schedules in release-4.23 and 5.0. If the kubevirt infra issues affect all releases, those are still burning CI time. Were 4.23/5.0 intentionally left out?
3 participants
These kubevirt CI jobs have had 0% pass rate for months, wasting thousands of hours of CI time. Set them to run once a year instead of removing them entirely.
Jobs affected:
release-4.19:
release-4.20:
release-4.21:
release-4.22:
Disable permafailing hypershift-kubevirt periodic CI jobs
This PR reduces CI resource waste in the OpenShift release repository by scaling back the frequency of several permafailing Hypershift KubeVirt periodic jobs. It updates CI job schedules in ci-operator config for the hypershift component so the jobs run only once per year (on May 17th) instead of daily or multiple times per day, preserving job definitions while avoiding continuous failures.
What's changing
Implementation
Rationale