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.

Sign up for GitHub

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

Jump to bottom

test failed: TestWatchRestore #9086

Closed
xiang90 opened this issue Jan 3, 2018 · 2 comments
Closed

test failed: TestWatchRestore #9086

xiang90 opened this issue Jan 3, 2018 · 2 comments
Assignees
@spzala
Milestone
etcd-v3.4

Comments

@xiang90
Copy link
Contributor

xiang90 commented Jan 3, 2018 

--- FAIL: TestWatchRestore (1.01s)
	watchable_store_test.go:328: failed to receive event in 1 second.

/cc @spzala
@xiang90 xiang90 mentioned this issue Jan 3, 2018
Merged
@spzala
Copy link
Member

spzala commented Jan 3, 2018

Thanks @xiang90 I will be digging into this.

@xiang90 xiang90 added this to the v3.4.0 milestone Jan 6, 2018
This was referenced Feb 1, 2018
Merged
Merged
@xiang90
Copy link
Contributor Author

xiang90 commented Feb 6, 2018

closed by #9281

@xiang90 xiang90 closed this as completed Feb 6, 2018
@jpbetz jpbetz mentioned this issue Mar 9, 2018
Merged
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Mar 13, 2018
Merge pull request #60998 from jpbetz/etcd-3.1.12
b651ed5 
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
@k8s-publishing-bot
Merge pull request #60998 from jpbetz/etcd-3.1.12
f6ece11 
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
@k8s-publishing-bot
Merge pull request #60998 from jpbetz/etcd-3.1.12
db21c95 
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
@k8s-publishing-bot
Merge pull request #60998 from jpbetz/etcd-3.1.12
67381c3 
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
@k8s-publishing-bot
Merge pull request #60998 from jpbetz/etcd-3.1.12
42d3b5e 
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
@k8s-publishing-bot
Merge pull request #60998 from jpbetz/etcd-3.1.12
7b860b2 
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
Assignees

@spzala spzala

Labels
None yet
Milestone
etcd-v3.4
Development

No branches or pull requests
2 participants
@xiang90 @spzala