-
Notifications
You must be signed in to change notification settings - Fork 132
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
NO-JIRA: restrict etcdctl defrag
to single member
#1394
NO-JIRA: restrict etcdctl defrag
to single member
#1394
Conversation
@Elbehery: This pull request explicitly references no jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
cc @benluddy |
@benluddy has faced this issue 2 weeks ago cluster-etcd-operator/test/e2e/etcdctl_test.go Lines 25 to 36 in c956ac3
|
I had the same issue here #1391 (comment) although running the test against a cluster passed from first run 🤔 |
When I saw this, etcdctl was timing out but the defrag completed on the last member after a few seconds. Could you set a more generous timeout on the etcdctl invocation instead of skipping it? I don't have a sense of how important this test coverage is. |
I think the issue is that this defrags all members, but there is no guarantee that all members are really up and running at the time. One might be down with a static pod rollout and then your call times out. Timeout might work, but would be 5-10m to withstand a static pod rollout. Maybe you can scope this down with --endpoints to a known pod that's up and running instead |
let me try this, I would go for |
8d47e9c
to
4135910
Compare
now it is
let see |
yeah that could work |
4135910
to
6958d4d
Compare
Failed with msg
The test runs within The erros is cause by etcd checks, that no flag overrides any envVar in use. The workaround is to lets see 🤞🏽 |
6958d4d
to
c23edad
Compare
trying diff approach
|
tested against CRC cluster
|
etcdctl defrag
to single member
/retest-required |
1 similar comment
/retest-required |
ran the test against a 4.19 cluster, and everything is fine
|
/retest-required |
|
/retest-required |
1 similar comment
/retest-required |
/label tide/merge-method-squash |
/retest-required |
@Elbehery: The following tests failed, say
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. |
/retest-required |
/test e2e-operator-fips |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Elbehery, tjungblu 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 |
/label acknowledge-critical-fixes-only |
5bbe494
into
openshift:master
[ART PR BUILD NOTIFIER] Distgit: cluster-etcd-operator |
Most of
etcdctl
e2e test are disabled by default.During last weeks, this test has failed most of the time, from changes that is non related to it.
It is better to disable it, as it blocks more important work, for no reason.
cc @tjungblu