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

UPSTREAM: <carry>: add audit annotations to track etcd state #2170

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

deads2k
Copy link

@deads2k deads2k commented Jan 13, 2025

We can use these annotations in a monitortest to start counting how many seconds we appear to lose etcd leadership for and what percentage of etcd requests fail during that time.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 13, 2025
@openshift-ci-robot
Copy link

@deads2k: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 13, 2025
@deads2k
Copy link
Author

deads2k commented Jan 14, 2025

very strange

/retest

@deads2k deads2k added backports/validated-commits Indicates that all commits come to merged upstream PRs. acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Jan 14, 2025
We can reconsider this if we have field size issues, but I doubt we
will.  If we do, we can find a way to configure this only during
pre-release we gain a lot of useful CI data.
@deads2k deads2k force-pushed the etcd-audit-annotation branch from cccaf3c to bc8ac76 Compare January 14, 2025 20:41
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. and removed backports/validated-commits Indicates that all commits come to merged upstream PRs. labels Jan 14, 2025
@openshift-ci-robot
Copy link

@deads2k: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@benluddy
Copy link

/lgtm

Discussed and accepted the increase in the serialized size of audit log entries in exchange for having the latency annotations all the time.

/hold

for proof

@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 Jan 14, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2025
Copy link

openshift-ci bot commented Jan 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, deads2k

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

@deads2k
Copy link
Author

deads2k commented Jan 14, 2025

/hold

No "no leader" annotations in the audit, but clients definitely say they appeared. Who's lying! I'll check in the morning

Copy link

openshift-ci bot commented Jan 30, 2025

@deads2k: 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-serial bc8ac76 link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-hypershift bc8ac76 link true /test e2e-aws-ovn-hypershift

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants