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.

[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 (wduan@redhat.com), 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

[jsafrane]

/lgtm
/approve
/verified by CI

[openshift-ci-robot]

@jsafrane: This PR has been marked as verified by CI.

Details

In response to this:

/lgtm
/approve
/verified by 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.

[dgoodwin]

/payload-job periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview-serial

This is the job where this continues to fail.

[openshift-ci]

@dgoodwin: 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.21-e2e-vsphere-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5a9b11e0-f30a-11f0-83e2-6bf6cff69797-0

[dgoodwin]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview-serial 4

[openshift-ci]

@dgoodwin: 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.21-e2e-vsphere-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/639188b0-f30a-11f0-90de-2a195e27f1a2-0

[Phaow]

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-ovn-techpreview-serial 4

[openshift-ci]

@Phaow: 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.21-e2e-vsphere-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/da3b3800-f4d9-11f0-8525-1105cfb128e8-0

[Phaow]

/test okd-scos-images

[dgoodwin]

Lot of discussion in the bug, not sure this PR is sufficient for what's going on https://issues.redhat.com/browse/OCPBUGS-65674

[dgoodwin]

/lgtm

It looks like this should alleviate most of the problem after discussion.

Please ensure this gets backported to 4.21 asap.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, jsafrane, RomanBednar

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:

• OWNERS [dgoodwin]

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]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 3c5cc33 and 2 for PR HEAD 8deb29e in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 1b6ece3 and 1 for PR HEAD 8deb29e in total

[jsafrane]

/retest-required

[dgoodwin]

/override ci/prow/e2e-aws-csi

unrelated

[openshift-ci]

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-csi

Details

In response to this:

/override ci/prow/e2e-aws-csi

unrelated

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.

[openshift-ci]

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

[openshift-ci-robot]

@RomanBednar: Jira Issue Verification Checks: Jira Issue OCPBUGS-65674
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-65674 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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.

[RomanBednar]

/override ci/prow/e2e-aws-csi

@dgoodwin We'll investigate CSI tests further for possible leaks in scope of: https://issues.redhat.com/browse/OCPBUGS-74212

[dgoodwin]

/cherry-pick release-4.21

I'll kick this off but please shepherd the resulting PR through to 4.21.

[openshift-cherrypick-robot]

@dgoodwin: #30654 failed to apply on top of branch "release-4.21":

Applying: VsphereConfigurationTestsRollOutTooOften event matcher should use broader regex
Using index info to reconstruct a base tree...
M	pkg/monitortestlibrary/pathologicaleventlibrary/duplicated_event_patterns.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/monitortestlibrary/pathologicaleventlibrary/duplicated_event_patterns.go
CONFLICT (content): Merge conflict in pkg/monitortestlibrary/pathologicaleventlibrary/duplicated_event_patterns.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 VsphereConfigurationTestsRollOutTooOften event matcher should use broader regex

Details

In response to this:

/cherry-pick release-4.21

I'll kick this off but please shepherd the resulting PR through to 4.21.

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.