OCPBUGS-65674: VsphereConfigurationTestsRollOutTooOften event matcher should use broader regex

[RomanBednar]

This is a followup to #30547 - we need to match secret related events now. The regex used here should be broad enough to prevent hitting these failures in CI.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@RomanBednar: This pull request references Jira Issue OCPBUGS-65674, which is invalid:

• expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

This is a followup to #30547 - we need to match secret related events now. The regex used here should be broad enough to prevent hitting these failures in CI.

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: RomanBednar
Once this PR has been reviewed and has the lgtm label, please assign xueqzhan 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

[RomanBednar]

/payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc

[openshift-ci]

@RomanBednar: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bb8dd310-eaf0-11f0-97e1-a19228820109-0

[RomanBednar]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

Details

In response to this:

/jira refresh

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.

[jsafrane]

{  3 events happened too frequently

event happened 32 times, something is wrong: namespace/openshift-cluster-csi-drivers daemonset/vmware-vsphere-csi-driver-node hmsg/9aaaed172e - reason/SuccessfulCreate (combined from similar events): Created pod: vmware-vsphere-csi-driver-node-7xqw4 (14:42:51Z) result=reject 
event happened 33 times, something is wrong: namespace/openshift-cluster-csi-drivers daemonset/vmware-vsphere-csi-driver-node hmsg/45b998d213 - reason/SuccessfulCreate (combined from similar events): Created pod: vmware-vsphere-csi-driver-node-kcl8h (14:50:20Z) result=reject 
event happened 46 times, something is wrong: namespace/openshift-cluster-csi-drivers daemonset/vmware-vsphere-csi-driver-node hmsg/2b77a94a11 - reason/SuccessfulCreate (combined from similar events): Created pod: vmware-vsphere-csi-driver-node-jbwhg (14:57:00Z) result=reject }

[RomanBednar]

/payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc

[openshift-ci]

@RomanBednar: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ca69c300-eba7-11f0-8acc-5b5614acb69d-0

[RomanBednar]

Yeah, I forgot the messages are inconsistent. Let's make it even less specific.

[jsafrane]

/payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc
the previous run did not have any storage issues, but it had some problems pulling images

[openshift-ci]

@jsafrane: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.22-e2e-vsphere-ovn-serial-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/154119e0-ec67-11f0-9218-a724fbcbccbb-0

[jsafrane]

/test e2e-aws-csi e2e-aws-ovn-fips

[jsafrane]

/test e2e-aws-ovn-microshift e2e-aws-ovn-microshift-serial e2e-aws-ovn-serial e2e-gcp-csi e2e-gcp-ovn e2e-gcp-ovn-upgrade e2e-metal-ipi-ovn-ipv6 e2e-vsphere-ovn e2e-vsphere-ovn-upi

[jsafrane]

/test e2e-aws-ovn-serial-1of2 e2e-aws-ovn-serial-2of2