OCPBUGS-48126: kubeapiserver auditloganalyzer: show resources updated too often

[vrutkovs]

Along with users issuing too many updates its useful to list resources being updated often. Several users may update a single resource, so they may not show up in existing tests.

This PR adds another set of flaking tests resource <group>.<resource>/<name> [-n <namespace>] has been updated too often with error message similar to resource <group>.<resource>/<name> [-n <namespace>] had <n> applies, check the audit log and operator log to figure out why details in audit log

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[vrutkovs]

/test e2e-aws-ovn

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[vrutkovs]

/test e2e-aws-ovn

[vrutkovs]

/test e2e-aws-ovn

[vrutkovs]

/test e2e-aws-ovn

[vrutkovs]

/test e2e-aws-ovn

[openshift-ci-robot]

@vrutkovs: This pull request references Jira Issue OCPBUGS-48126, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

In 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.

[openshift-ci-robot]

@vrutkovs: This pull request references Jira Issue OCPBUGS-48126, which is valid.

3 validation(s) were run on this bug

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

In response to this:

Along with users issuing too many updates its useful to list resources being updated often. Several users may update a single resource, so they may not show up in existing tests.

This PR adds another set of flaking tests resource <group>.<resource>/<name> [-n <namespace>] has been updated too often with error message similar to resource <group>.<resource>/<name> [-n <namespace>] had <n> applies, check the audit log and operator log to figure out why details in audit log

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.

[vrutkovs]

/retest

[openshift-ci]

@vrutkovs: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-openstack-ovn	627ee17	link	false	/test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd	627ee17	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-ovn	627ee17	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	627ee17	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn-ipv6	627ee17	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

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.