OCPBUGS-3101: Rebase openshift/etcd 4.11 onto v3.5.6 #170
Conversation
…g-jwt/jwt/v4 Signed-off-by: haimantika mitra <haimantikamitra@gmail.com> Signed-off-by: Davanum Srinivas <davanum@gmail.com>
…-release-3.5 Replace github.com/form3tech-oss/jwt-go with https://github.com/golang-jwt/jwt
Signed-off-by: Allen Ray <alray@redhat.com>
Signed-off-by: Hitoshi Mitake <h.mitake@gmail.com>
Signed-off-by: Hitoshi Mitake <h.mitake@gmail.com>
Backport PR 14322 to release-3.5
Signed-off-by: Kafuu Chino <KafuuChinoQ@gmail.com> add test 1 1 1 1 1 1
*: avoid closing a watch with ID 0 incorrectly
Signed-off-by: Manuel Rüger <manuel@rueg.eu>
ubuntu 20.10 is EOL and fails with E: The repository 'http://security.ubuntu.com/ubuntu groovy-security Release' does not have a Release file. Signed-off-by: Manuel Rüger <manuel@rueg.eu>
If one of the nodes in the cluster has lost a dns record, restarting the second node will break it. This PR makes an attempt to add a comparison without using a resolver, which allows to protect cluster from dns errors and does not break the current logic of comparing urls in the URLStringsEqual function. You can read more in the issue etcd-io#7798 Fixes etcd-io#7798 Signed-off-by: Prasad Chandrasekaran <prasadc@vmware.com>
Co-authored-by: Lili Cosic <cosiclili@gmail.com> Signed-off-by: Prasad Chandrasekaran <prasadc@vmware.com>
Signed-off-by: Prasad Chandrasekaran <prasadc@vmware.com>
Automated cherry pick of etcd-io#13224 etcd-io#14572
Signed-off-by: Benjamin Wang <wachao@vmware.com>
[3.5] etcdserver: added more debug log for the purgeFile goroutine
[Release-3.5] Makefile: additional logic fix / Update Ubuntu base
…able The client retries connection without backoff when the server is gone after the watch stream is established. This results in high CPU usage in the client process. This change introduces backoff when the stream is failed and unavailable. Signed-off-by: Hisanobu Tomari <posco.grubb@gmail.com>
…-3.5 [3.5] client/v3: Add backoff before retry when watch stream returns unavailable
Release-3.5: server/etcdmain: add configurable cipher list to gRPC proxy listener
Signed-off-by: 王霄霄 <1141195807@qq.com>
…-3.5 Backport etcd-io#14591 to 3.5.
…PermCache Signed-off-by: Hitoshi Mitake <h.mitake@gmail.com>
…d-io#14574 Signed-off-by: Oleg Guba <oleg@dropbox.com> Signed-off-by: Hitoshi Mitake <h.mitake@gmail.com>
[3.5] server: refresh auth info when etcd recovers from a snapshot
…o when recovering from a snapshot Signed-off-by: Benjamin Wang <wachao@vmware.com>
test: added e2e test case for issue 14571: etcd doesn't load auth info when recovering from a snapshot
Check the client count before creating the ephemeral key, do not
create the key if there are already too many clients. Check the
count after creating the key again, if the total kvs is bigger
than the expected count, then check the rev of the current key,
and take action accordingly based on its rev. If its rev is in
the first ${count}, then it's valid client, otherwise, it should
fail.
Signed-off-by: Benjamin Wang <wachao@vmware.com>
Signed-off-by: jianfei.zhang <jianfei.zhang@daocloud.io>
[3.5] fix: close maintenance conn
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dusk125, 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 cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
/jira refresh |
|
@tjungblu: This pull request references Jira Issue OCPBUGS-3101, which is invalid:
Comment 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 kubernetes/test-infra repository. |
|
@geliu2016 did you get a chance to test OCPBUGS-3100 already? |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@tjungblu: This pull request references Jira Issue OCPBUGS-3101, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
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 kubernetes/test-infra repository. |
|
/retest-required |
5 similar comments
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
|
@tjungblu: all tests passed! 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. |
|
@tjungblu: An error was encountered searching for bug OCPBUGS-3101 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 401:
Please contact an administrator to resolve this issue, then request a bug refresh with 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 kubernetes/test-infra repository. |
No description provided.