-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
test failed: TestWatchRestore #9086
Milestone
Comments
Thanks @xiang90 I will be digging into this. |
This was referenced Feb 1, 2018
closed by #9281 |
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this issue
Mar 13, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars
k8s-publishing-bot
added a commit
to kubernetes/sample-apiserver
that referenced
this issue
Mar 13, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars Kubernetes-commit: b651ed5ea7331139fc39ea84a55b0261c6b3f000
k8s-publishing-bot
added a commit
to kubernetes/apiextensions-apiserver
that referenced
this issue
Mar 13, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars Kubernetes-commit: b651ed5ea7331139fc39ea84a55b0261c6b3f000
sttts
pushed a commit
to sttts/sample-apiserver
that referenced
this issue
Mar 16, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars Kubernetes-commit: b651ed5ea7331139fc39ea84a55b0261c6b3f000
sttts
pushed a commit
to sttts/apiextensions-apiserver
that referenced
this issue
Mar 16, 2018
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars Kubernetes-commit: b651ed5ea7331139fc39ea84a55b0261c6b3f000
openshift-publish-robot
pushed a commit
to openshift/kubernetes-sample-apiserver
that referenced
this issue
Jan 14, 2019
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Bump to etcd 3.1.12 to pick up critical fix etcd [3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes: Fix [mvcc "unsynced" watcher restore operation](etcd-io/etcd#9297). - "unsynced" watcher is watcher that needs to be in sync with events that have happened. - That is, "unsynced" watcher is the slow watcher that was requested on old revision. - "unsynced" watcher restore operation was not correctly populating its underlying watcher group. - Which possibly causes [missing events from "unsynced" watchers](etcd-io/etcd#9086). This will be backported to 1.9 as well. Release note: ```release-note Upgrade the default etcd server version to 3.1.12 to pick up critical etcd "mvcc "unsynced" watcher restore operation" fix. ``` cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars Kubernetes-commit: b651ed5ea7331139fc39ea84a55b0261c6b3f000
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/cc @spzala
The text was updated successfully, but these errors were encountered: