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

Jump to bottom

[release-4.10] no pending on etcdHighNumberOfLeaderChanges 1st 1h #804

Closed
wants to merge 1 commit into from
Closed

[release-4.10] no pending on etcdHighNumberOfLeaderChanges 1st 1h #804

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #783

/assign mfojtik

@jluhrsen
no pending on etcdHighNumberOfLeaderChanges 1st 1h
600e07e 
during initial cluster roll-out there is enough churn that etcd
leadership will change and these alerts would result. This can
result of normal cluster installation and the alerts could cause
false concern of some problem.

this is happening more frquently in CI with OVN as the CNI,
especially in the GCP cloud (for whatever reason) and results
in extra failures in CI, as well as alarms customers would
see.

This should wait for an hour after "cluster_version" goes
initial and should provide enough time before the alert would
be much more meaningful if it came.

Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 27, 2022
Merged
@openshift-ci openshift-ci bot requested review from Elbehery and EmilyM1 April 27, 2022 07:36
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 27, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
To complete the pull request process, please assign sttts after the PR has been reviewed.
You can assign the PR to them by writing /assign @sttts in a comment when ready.

The full list of commands accepted by this bot can be found 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

@mfojtik
Copy link
Member

mfojtik commented Apr 27, 2022

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 27, 2022
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2022
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 26, 2022
@openshift-merge-robot
Copy link
Contributor

@openshift-cherrypick-robot: PR needs rebase.

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
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 26, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 7, 2022

@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-gcp-five-control-plane-replicas 600e07e link false /test e2e-gcp-five-control-plane-replicas
ci/prow/e2e-operator 600e07e link true /test e2e-operator
ci/prow/e2e-aws-single-node 600e07e link true /test e2e-aws-single-node
ci/prow/e2e-agnostic-upgrade 600e07e link true /test e2e-agnostic-upgrade
ci/prow/configmap-scale 600e07e link true /test configmap-scale
ci/prow/e2e-agnostic 600e07e link true /test e2e-agnostic

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.

@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Oct 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 8, 2022

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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
Reviewers

@Elbehery Elbehery Awaiting requested review from Elbehery

@EmilyM1 EmilyM1 Awaiting requested review from EmilyM1

Assignees

@mfojtik mfojtik

Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
5 participants
@openshift-cherrypick-robot @mfojtik @openshift-bot @openshift-merge-robot @jluhrsen