k8s-merge-robot be104a8271 Merge pull request #25415 from hongchaodeng/e2 ...

Automatic merge from submit-queue

etcd_watcher: make Deleted Event.Object's version consistent

### What's the problem?

In [sendDelete()](995f022808/pkg/storage/etcd/etcd_watcher.go (L437-L442)), Deleted Event.Object's resource version will be set to the latest resource version. This is actually an assumption made by cacher that all later events should have objects with larger verions; See [here](995f022808/pkg/storage/cacher.go (L579-L581)).

In sendModify(), it could also return Deleted event. However, the resource version is still the old version, which is inconsistent behavior with sendDelete().

### What's this PR?
This PR sets the version of oldObj in sendModify() to be the latest version.
Provided unit test for it.

2016-05-14 20:46:20 -07:00

..

etcd

etcd_watcher: test for ensuring delete event have latest index

2016-05-12 11:01:26 -07:00

etcd3

etcd3/watcher: refactor test

2016-05-10 12:37:31 -07:00

storagebackend

start etcd compactor in background

2016-05-04 16:01:03 -07:00

testing

It's 2016, yo.

2016-05-13 12:41:40 -07:00

cacher_test.go

Return 'too old' errors from watch cache via watch stream

2016-05-10 10:59:53 -04:00

cacher.go

Return 'too old' errors from watch cache via watch stream

2016-05-10 10:59:53 -04:00

doc.go

…

errors.go

…

interfaces.go

Decouple etcd node.expiration logic from DeleitonTimestamp

2016-04-13 15:11:53 -07:00

util_test.go

…

util.go

…

watch_cache_test.go

Make watch cache behave like uncached watch

2016-04-12 10:14:07 -04:00

watch_cache.go

Honor starting resourceVersion in watch cache

2016-04-14 09:37:22 -04:00