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.

Sign up for GitHub

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

Jump to bottom

[release-4.6] Bug 2000502: bump SystemMemoryExceedsReservation alert threshold to 95% #2750

Merged

openshift-merge-robot merged 1 commit into openshift:release-4.6 from harche:bug_2000502

Oct 15, 2021

Contributor

harche commented Sep 2, 2021

This is a backport of #2749

- What I did

- How to verify it

- Description for the changelog


          bump SystemMemoryExceedsReservation alert threshold to 95%

fa7b5be

In order to reduce the excessive firing of this alert we
are making it fire at 95% of system memory utilization
instead of the current 90 %. By making this change, we
hope to keep this alert still relevant for users while
reducing the noise.

Signed-off-by: Harshal Patil <harpatil@redhat.com>

openshift-ci bot added bugzilla/severity-medium bugzilla/invalid-bug labels

Contributor

openshift-ci bot commented Sep 2, 2021

@harche: This pull request references Bugzilla bug 2000502, which is invalid:

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW 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 2000502: bump SystemMemoryExceedsReservation alert threshold to 95%

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 bot requested review from cgwalters and kikisdeliveryservice

September 2, 2021 09:50

Contributor

openshift-ci bot commented Sep 2, 2021 •

edited

@harche: 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-vsphere-upgrade	`fa7b5be`	link	`/test e2e-vsphere-upgrade`
ci/prow/e2e-metal-ipi	`fa7b5be`	link	`/test e2e-metal-ipi`
ci/prow/okd-e2e-aws	`fa7b5be`	link	`/test okd-e2e-aws`
ci/prow/e2e-aws-workers-rhel7	`fa7b5be`	link	`/test e2e-aws-workers-rhel7`
ci/prow/okd-e2e-gcp-op	`fa7b5be`	link	`/test okd-e2e-gcp-op`
ci/prow/okd-e2e-upgrade	`fa7b5be`	link	`/test okd-e2e-upgrade`

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.

Contributor

rphillips commented Sep 14, 2021

/lgtm

openshift-ci bot assigned rphillips

openshift-ci bot added the lgtm label

sinnykumari approved these changes

View reviewed changes

Contributor

openshift-ci bot commented Sep 14, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, rphillips, sinnykumari

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

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

openshift-ci bot added the approved label

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

16 similar comments

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

openshift-bot commented Sep 14, 2021

/retest-required

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

Contributor

kikisdeliveryservice commented Sep 28, 2021

/bugzilla refresh

Contributor

openshift-ci bot commented Sep 28, 2021

@kikisdeliveryservice: This pull request references Bugzilla bug 2000502, which is invalid:

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Sep 29, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Sep 29, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Sep 30, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Sep 30, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 1, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 1, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 2, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 2, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 3, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 3, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 4, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 4, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 5, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 5, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 6, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 6, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 7, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 7, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 8, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

Contributor

openshift-ci bot commented Oct 8, 2021

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

expected dependent Bugzilla bug 2000501 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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:

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

Contributor

openshift-bot commented Oct 9, 2021

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci bot added bugzilla/valid-bug and removed bugzilla/invalid-bug labels

Contributor

openshift-ci bot commented Oct 9, 2021

@openshift-bot: This pull request references Bugzilla bug 2000502, which is valid. The bug has been moved to the POST state. 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 NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2000501 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2000501 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request.

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.

sdodson added cherry-pick-approved backport-risk-assessed labels

openshift-merge-robot merged commit c0b5ea5 into openshift:release-4.6

Contributor

openshift-ci bot commented Oct 15, 2021

@harche: All pull requests linked via external trackers have merged:

openshift/machine-config-operator#2750

Bugzilla bug 2000502 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 2000502: bump SystemMemoryExceedsReservation alert threshold to 95%

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 backport-risk-assessed bugzilla/severity-medium bugzilla/valid-bug cherry-pick-approved lgtm