[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi #740

openshift-cherrypick-robot · 2020-10-13T22:54:56Z

This is an automated cherry-pick of #735

/assign periklis

openshift-ci-robot · 2020-10-13T22:56:03Z

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug 1886856 on the Bugzilla server at https://bugzilla.redhat.com:

response code 502 not 200
Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

In response to this:

[release-4.6] Bug 1886856: Increase es proxy default memory resources to 256Mi

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.

periklis · 2020-10-14T06:18:25Z

/lgtm

ewolinetz · 2020-10-14T16:18:57Z

/approve

openshift-ci-robot · 2020-10-14T16:19:17Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ewolinetz, openshift-cherrypick-robot, periklis

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:

~~OWNERS~~ [ewolinetz]

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

periklis · 2020-10-15T07:17:58Z

/bugzilla refresh

openshift-ci-robot · 2020-10-15T07:18:02Z

@periklis: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.0" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

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

openshift-bot · 2020-10-16T01:00:12Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-16T01:00:15Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.0" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-17T01:01:04Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-17T01:01:07Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.0" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-20T01:00:33Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-20T01:00:35Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.0" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-21T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-21T01:01:16Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.0" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-22T01:00:35Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-22T01:00:45Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.z" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-23T01:01:18Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-23T01:01:21Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.z" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-24T01:00:59Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-24T01:01:01Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.z" release, but it targets "4.7.0" instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot · 2020-10-25T01:00:44Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-10-27T01:01:12Z

@openshift-bot: This pull request references Bugzilla bug 1886856, which is invalid:

expected the bug to target the "4.6.z" release, but it targets "4.7.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is ON_QA instead
expected Bugzilla bug 1886856 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

periklis · 2020-11-02T13:08:55Z

/retitle [release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

openshift-ci-robot · 2020-11-02T13:09:15Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1880960, which is invalid:

expected dependent Bugzilla bug 1886856 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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

In response to this:

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

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.

periklis · 2020-11-04T07:17:19Z

/bugzilla refresh

openshift-ci-robot · 2020-11-04T07:17:27Z

@periklis: This pull request references Bugzilla bug 1880960, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.6.z) matches configured target release for branch (4.6.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1886856 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
dependent Bugzilla bug 1886856 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0
bug has dependents

In response to this:

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

periklis · 2020-11-19T08:08:49Z

/cherry-pick release-4.5

openshift-cherrypick-robot · 2020-11-19T08:08:50Z

@periklis: once the present PR merges, I will cherry-pick it on top of release-4.5 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.5

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.

periklis · 2020-11-19T15:19:16Z

/bugzilla refresh

openshift-ci-robot · 2020-11-19T15:19:22Z

@periklis: This pull request references Bugzilla bug 1880960, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.6.z) matches configured target release for branch (4.6.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1886856 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
dependent Bugzilla bug 1886856 targets the "4.7.0" release, which is one of the valid target releases: 4.7.0
bug has dependents

In response to this:

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

sdodson · 2020-11-20T01:55:23Z

Oops, just saw openshift/elasticsearch-operator#528 (comment) so clearing the approval I just added.

openshift-bot · 2020-11-20T17:55:56Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-11-20T18:08:49Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci-robot · 2020-11-20T20:44:25Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 1880960 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

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-cherrypick-robot · 2020-11-20T20:44:43Z

@periklis: new pull request created: #808

In response to this:

/cherry-pick release-4.5

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.

…ry-pick-735-to-release-4.6 [release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi

Bug 1886856: Increase es proxy default memory resources to 256Mi

21dd8d2

openshift-cherrypick-robot mentioned this pull request Oct 13, 2020

Bug 1886856: Increase es proxy default memory resources to 256Mi #735

Merged

openshift-ci-robot assigned periklis Oct 13, 2020

openshift-ci-robot requested review from ewolinetz and jcantrill October 13, 2020 22:56

openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2020

openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 14, 2020

openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 15, 2020

openshift-ci-robot changed the title ~~[release-4.6] Bug 1886856: Increase es proxy default memory resources to 256Mi~~ [release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi Nov 2, 2020

openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 4, 2020

jcantrill added the release/4.6 label Nov 10, 2020

openshift-ci-robot mentioned this pull request Nov 18, 2020

[release-4.6] Bug 1880960: Add typhoeus for keep-alives in elasticsearch plugin openshift/origin-aggregated-logging#2017

Merged

openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. and removed bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. labels Nov 19, 2020

openshift-ci-robot mentioned this pull request Nov 19, 2020

[release-4.6] Bug 1880960: Fix keep-alive configuration openshift/elasticsearch-proxy#61

Merged

sdodson added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Nov 20, 2020

openshift-ci-robot mentioned this pull request Nov 20, 2020

[release-4.6] Bug 1880960: Add keep-alive backend for elasticsearch store #760

Merged

ecordell added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 20, 2020

openshift-ci-robot mentioned this pull request Nov 20, 2020

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi openshift/elasticsearch-operator#528

Merged

openshift-merge-robot merged commit 4f9445c into openshift:release-4.6 Nov 20, 2020

openshift-cherrypick-robot mentioned this pull request Nov 20, 2020

[release-4.5] Bug 1899419: Increase es proxy default memory resources to 256Mi #808

Merged

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi #740

[release-4.6] Bug 1880960: Increase es proxy default memory resources to 256Mi #740

Uh oh!

Conversation

openshift-cherrypick-robot commented Oct 13, 2020

Uh oh!

openshift-ci-robot commented Oct 13, 2020

Uh oh!

periklis commented Oct 14, 2020

Uh oh!

ewolinetz commented Oct 14, 2020

Uh oh!

openshift-ci-robot commented Oct 14, 2020

Uh oh!

periklis commented Oct 15, 2020

Uh oh!

openshift-ci-robot commented Oct 15, 2020

Uh oh!

openshift-bot commented Oct 16, 2020

Uh oh!

openshift-ci-robot commented Oct 16, 2020

Uh oh!

openshift-bot commented Oct 17, 2020

Uh oh!

openshift-ci-robot commented Oct 17, 2020

Uh oh!

openshift-bot commented Oct 20, 2020

Uh oh!

openshift-ci-robot commented Oct 20, 2020

Uh oh!

openshift-bot commented Oct 21, 2020

Uh oh!

openshift-ci-robot commented Oct 21, 2020

Uh oh!

openshift-bot commented Oct 22, 2020

Uh oh!

openshift-ci-robot commented Oct 22, 2020

Uh oh!

openshift-bot commented Oct 23, 2020

Uh oh!

openshift-ci-robot commented Oct 23, 2020

Uh oh!

openshift-bot commented Oct 24, 2020

Uh oh!

openshift-ci-robot commented Oct 24, 2020

Uh oh!

openshift-bot commented Oct 25, 2020

Uh oh!

openshift-ci-robot commented Oct 27, 2020

Uh oh!

periklis commented Nov 2, 2020

Uh oh!

openshift-ci-robot commented Nov 2, 2020

Uh oh!

periklis commented Nov 4, 2020

Uh oh!

openshift-ci-robot commented Nov 4, 2020

Uh oh!

periklis commented Nov 19, 2020

Uh oh!

openshift-cherrypick-robot commented Nov 19, 2020

Uh oh!

periklis commented Nov 19, 2020

Uh oh!

openshift-ci-robot commented Nov 19, 2020

Uh oh!

sdodson commented Nov 20, 2020

Uh oh!

openshift-bot commented Nov 20, 2020

Uh oh!

openshift-bot commented Nov 20, 2020

Uh oh!

openshift-ci-robot commented Nov 20, 2020

Uh oh!

openshift-cherrypick-robot commented Nov 20, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects