Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.14] OCPBUGS-22411: fix: increase upper bounds for samples operator #28356

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #28353

/assign eggfoobar

Samples Operator added another watching triggerig the upper bound for SNO.

The upper limit was calculated to 52 via curl command below, increasing to 27*2 to buffer the change.

```
curl -L https://search.ci.openshift.org/\?search\=.\*Operator.\*cluster-samples.\*produces+more+watch+requests+than+expected\&maxAge\=168h\&context\=1\&type\=junit\&name\=aws.\*single-node\&excludeName\=\&maxMatches\=5\&maxBytes\=20971520\&groupBy\=job | grep watchrequestcount= | cut -d= -f2 | cut -d, -f1
```

Signed-off-by: ehila <ehila@redhat.com>
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-22358 has been cloned as Jira Issue OCPBUGS-22411. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-22411: fix: increase upper bounds for samples operator

In response to this:

This is an automated cherry-pick of #28353

/assign eggfoobar

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/test-infra repository.

@openshift-ci openshift-ci bot changed the title [release-4.14] OCPBUGS-22358: fix: increase upper bounds for samples operator [release-4.14] OCPBUGS-22411: fix: increase upper bounds for samples operator Oct 25, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 25, 2023
@openshift-ci-robot
Copy link

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-22358 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-22358 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

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

In response to this:

This is an automated cherry-pick of #28353

/assign eggfoobar

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/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 25, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 27, 2023
@jeff-roche
Copy link
Contributor

/retest

@neisw
Copy link
Contributor

neisw commented Oct 30, 2023

/label backport-risk-assessed

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 30, 2023

@neisw: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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/test-infra repository.

@jeff-roche
Copy link
Contributor

/assign @bparees

@jupierce
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 31, 2023
@bparees
Copy link
Contributor

bparees commented Oct 31, 2023

/approve

@bparees bparees added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 31, 2023
Copy link
Contributor

openshift-ci bot commented Oct 31, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, eggfoobar, openshift-cherrypick-robot

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 31, 2023
@wangke19
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 31, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD cf6fcc2 and 2 for PR HEAD 0a14be9 in total

Copy link
Contributor

openshift-ci bot commented Oct 31, 2023

@openshift-cherrypick-robot: 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-aws-ovn-upgrade 0a14be9 link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-etcd-recovery 0a14be9 link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-single-node-upgrade 0a14be9 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn 0a14be9 link false /test e2e-openstack-ovn

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/test-infra repository. I understand the commands that are listed here.

@jeff-roche
Copy link
Contributor

/retest-required

@openshift-ci openshift-ci bot merged commit 81a21f1 into openshift:release-4.14 Nov 1, 2023
19 of 23 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-22411: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-22411 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #28353

/assign eggfoobar

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet