-
Notifications
You must be signed in to change notification settings - Fork 4.7k
etcd clusters must negotiate to reach v3 mode, wait #13261
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
etcd clusters must negotiate to reach v3 mode, wait #13261
Conversation
lgtm [merge] |
should kubernetes/kubernetes#39821 have done this as well? |
[Test]ing while waiting on the merge queue |
Only embedded servers have to do it. |
Otherwise we can start making calls to the cluster while it is still in v2 mode.
73f175a
to
9390478
Compare
Evaluated for origin test up to 9390478 |
ClusterVersion() can be nil, apparently. I have no version yet I must
negotiate, or something.
…On Mon, Mar 6, 2017 at 9:05 PM, OpenShift Bot ***@***.***> wrote:
continuous-integration/openshift-jenkins/test Running (
https://ci.openshift.redhat.com/jenkins/job/test_pull_
requests_origin_future/886/) (Base Commit: da719a3
<da719a3>
)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13261 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p9A5dIUSy4sT21IcbiQQjuyvUbfCks5rjLtqgaJpZM4MUswM>
.
|
Evaluated for origin merge up to 9390478 |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/887/) (Base Commit: da719a3) (Image: devenv-rhel7_6044) |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/886/) (Base Commit: da719a3) |
1 similar comment
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_future/886/) (Base Commit: da719a3) |
Otherwise we can start making calls to the cluster while it is still in v2 mode.
Fixes #12993
@liggitt