[openshift-cherrypick-robot]

This is an automated cherry-pick of #31733

/assign vr4manta

[openshift-merge-bot]

Pipeline controller notification

This PR uses the pipeline controller for second-stage tests. Selection and triggering follow the repository configuration.

Use /test ? to list jobs and /pipeline help for commands.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML; Path: .coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 645771ec-daf2-48a3-a4df-52c2a3f46738

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-130609 has been cloned as Jira Issue OCPBUGS-134608. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-134608: Fix pathological events

Details

In response to this:

This is an automated cherry-pick of #31733

/assign vr4manta

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-134608, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.z) matches configured target version for branch (4.21.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-130609 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-130609 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
• bug has dependents

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #31733

/assign vr4manta

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.

[redhat-chai-bot]

Chai test selection for eaa0f708db0a064069700b7ee56e017c66bfd268 → release-4.21

• pull-ci-openshift-origin-release-4.21-e2e-vsphere-ovn

Reason: Cherry-pick of #31733 modifying the vSphere CSI pathological event matcher (newVsphereConfigurationTestsRollOutTooOftenEventMatcher). Functional changes: time window padding widened from ±10 min to ±30 min on configuration test intervals, messageReasonRegex expanded with ^ScalingReplicaSet$, messageHumanRegex narrowed to vmware-vsphere-csi-driver, Jira ref updated. New unit tests passed in first-stage unit job. Selected e2e-vsphere-ovn as the sole vSphere e2e job — only vSphere clusters produce the openshift-cluster-csi-drivers namespace events and vmware-vsphere-csi-driver messages that the matcher targets. No other platform can exercise this code path. e2e-vsphere-ovn-upi uses the same monitor framework and CSI driver; one vSphere job covers the change. All other candidates (AWS, GCP, metal, MicroShift, KubeVirt, upgrade, serial, builds, image, FIPS, Jenkins) are unrelated — the matcher is vSphere-specific.

/test e2e-vsphere-ovn

[redhat-chai-bot]

/pipeline mark-pipeline-gate eaa0f70

[openshift-ci]

@openshift-cherrypick-robot: 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.