OCPBUGS-74917: bump marketplace-operator watch count limits

[neisw]

No description provided.

[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]

@neisw: This pull request references Jira Issue OCPBUGS-74917, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

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:

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]

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]

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

[dgoodwin]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, neisw

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,neisw]

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

[dgoodwin]

Actually I think I'll hold, I rage reworked this last night, I hope it's ready to review today.

/hold

[tmshort]

operator-marketplace now watches the apiserver.config.openshift.io/cluster resource for TLS profile support. This increase was expected.

[jianzhangbjz]

/verified by @jianzhangbjz

[openshift-ci-robot]

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

Details

In response to this:

/verified by @jianzhangbjz

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.

[jianzhangbjz]

Based on the https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_operator-framework-olm/1217/pull-ci-openshift-operator-framework-olm-main-e2e-gcp-ovn/2018519832512696320 logs,

[Monitor:audit-log-analyzer][sig-arch][Late] operators should not create watch channels very often expand_less0s{Operator "marketplace-operator" produces more watch requests than expected: watchrequestcount=39, upperbound=38, ratio=1.03  } | : [Monitor:audit-log-analyzer][sig-arch][Late] operators should not create watch channels very often expand_less | 0s | {Operator "marketplace-operator" produces more watch requests than expected: watchrequestcount=39, upperbound=38, ratio=1.03  }

Starting EventSource controller=catalogsource-controller source="kind source: *v1alpha1.CatalogSource"                                                                  
Starting EventSource controller=operatorhub-controller source="kind source: *v1.OperatorHub"                                                                            
Starting EventSource controller=configmap-controller source="kind source: *v1.ConfigMap"
...
OpenShift APIServer API available - setting up watch for APIServer TLS configuration                                                                                    
APIServer TLS configuration changed: profile=Intermediate (default), minVersion=TLS 1.2, cipherCount=9 

Watch resources:

• CatalogSource
• OperatorHub
• ConfigMap
• APIServer (New)

39 < 2*30 (https://github.com/openshift/origin/blob/main/pkg/monitortests/kubeapiserver/auditloganalyzer/handle_operator_watch_count_tracking.go#L464-L466). LGTM.

[jianzhangbjz]

/jira refresh

[openshift-ci-robot]

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-74917, 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 (jiazha@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.