[release-4.14]OCPBUGS-31354: add SNO control plane high cpu usage alert

qJkee commented 5 months ago

Manual backport of https://github.com/openshift/cluster-kube-apiserver-operator/pull/1680 and https://github.com/openshift/cluster-kube-apiserver-operator/pull/1676

openshift-ci-robot commented 5 months ago

@qJkee: This pull request references Jira Issue OCPBUGS-31354, which is invalid:

expected dependent Jira Issue OCPBUGS-33315 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707): >Manual backport of https://github.com/openshift/cluster-kube-apiserver-operator/pull/1680 and https://github.com/openshift/cluster-kube-apiserver-operator/pull/1676 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

p0lyn0mial commented 5 months ago

any conflicts when moving ?

wangke19 commented 4 months ago

The PR has been pre-merge verified and got the expected results. detail see https://issues.redhat.com/browse/OCPBUGS-31354?focusedId=25067523&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25067523****

wangke19 commented 4 months ago

/label qe-approved

openshift-ci-robot commented 4 months ago

@qJkee: This pull request references Jira Issue OCPBUGS-31354, which is invalid:

expected dependent Jira Issue OCPBUGS-35832 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707): >Manual backport of https://github.com/openshift/cluster-kube-apiserver-operator/pull/1680 and https://github.com/openshift/cluster-kube-apiserver-operator/pull/1676 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

wangke19 commented 4 months ago

/test e2e-azure-ovn

openshift-ci[bot] commented 4 months ago

@qJkee: 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-gcp-operator-single-node	2b4152a7ab58a9250468aa5a07acf5095b63ad4c	link	false	`/test e2e-gcp-operator-single-node`
ci/prow/e2e-aws-operator-disruptive-single-node	2b4152a7ab58a9250468aa5a07acf5095b63ad4c	link	false	`/test e2e-aws-operator-disruptive-single-node`
ci/prow/e2e-azure-ovn	2b4152a7ab58a9250468aa5a07acf5095b63ad4c	link	false	`/test e2e-azure-ovn`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

tkashem commented 4 months ago

any conflicts when moving ?

@qJkee was there any conflicts, can you please share the diffs?

p0lyn0mial commented 4 months ago

@qJkee was there any conflicts, can you please share the diffs?

@qJkee reached out to me via Slack, saying there was a small conflict in the starter.go file.

I have checked and the starter.go file matches 4.15 PR - https://github.com/openshift/cluster-kube-apiserver-operator/pull/1706/files#diff-0d623dfd885adb20f991bda4c2453aebd732ca6dbb4d1d4be6e79805c3b48de6

/lgtm

@tkashem please add the backport-risk-assessed label - thanks.

tkashem commented 4 months ago

/label backport-risk-assessed /approve

openshift-ci[bot] commented 4 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: p0lyn0mial, qJkee, tkashem

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](https://github.com/openshift/cluster-kube-apiserver-operator/blob/release-4.14/OWNERS)~~ [p0lyn0mial,tkashem] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

qJkee commented 4 months ago

/jira refresh

openshift-ci-robot commented 4 months ago

@qJkee: This pull request references Jira Issue OCPBUGS-31354, which is invalid:

expected dependent Jira Issue OCPBUGS-35832 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707#issuecomment-2210946839): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

wangke19 commented 4 months ago

/label cherry-pick-approved

wangke19 commented 4 months ago

/jira refresh

openshift-ci-robot commented 4 months ago

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

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-35832](https://issues.redhat.com//browse/OCPBUGS-35832) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-35832](https://issues.redhat.com//browse/OCPBUGS-35832) targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z * bug has dependents

Requesting review from QA contact: /cc @wangke19

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707#issuecomment-2212776154): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

wangke19 commented 4 months ago

/jira refresh

openshift-ci-robot commented 4 months ago

@wangke19: This pull request references Jira Issue OCPBUGS-31354, which is valid.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.14.z) matches configured target version for branch (4.14.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-35832](https://issues.redhat.com//browse/OCPBUGS-35832) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-35832](https://issues.redhat.com//browse/OCPBUGS-35832) targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z * bug has dependents

Requesting review from QA contact: /cc @wangke19

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707#issuecomment-2212778437): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-ci-robot commented 4 months ago

@qJkee: Jira Issue OCPBUGS-31354: All pull requests linked via external trackers have merged:

openshift/cluster-kube-apiserver-operator#1707

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

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1707): >Manual backport of https://github.com/openshift/cluster-kube-apiserver-operator/pull/1680 and https://github.com/openshift/cluster-kube-apiserver-operator/pull/1676 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-bot commented 4 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.14.0-202407080241.p0.g1fe5769.assembly.stream.el8 for distgit ose-cluster-kube-apiserver-operator. All builds following this will include this PR.

openshift-merge-robot commented 4 months ago

Fix included in accepted release 4.14.0-0.nightly-2024-07-08-131625

openshift / cluster-kube-apiserver-operator

[release-4.14]OCPBUGS-31354: add SNO control plane high cpu usage alert #1707