-
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
Add a simple test ensuring membership is properly bootstrapped #17014
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Marek Siarkowicz <[email protected]>
/retest |
fuweid
approved these changes
Nov 24, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ctl_v3_member_test.go:310:
Error Trace: /home/fuwei/go/src/go.etcd.io/etcd/tests/e2e/ctl_v3_member_test.go:310
Error: Received unexpected error:
match not found. Set EXPECT_DEBUG for more info Errs: [unexpected exit code [2] after running [/home/fuwei/go/src/go.etcd.io/etcd/bin/etcd --name TestRemoveNonExistingMember-test-0 --listen-client-urls http://localhost:20000 --advertise-client-urls http://localhost:20000 --listen-peer-urls http://localhost:20001 --initial-advertise-peer-urls http://localhost:20001 --initial-cluster-token new --data-dir /tmp/TestRemoveNonExistingMember3670107214/002 --snapshot-count 10000 --initial-cluster TestRemoveNonExistingMember-test-0=http://localhost:20001 --initial-cluster-state new]], last lines:
goroutine 50 [running]:
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x2?, 0x3?, {0x0?, 0x0?, 0xc0007400a0?})
go.uber.org/[email protected]/zapcore/entry.go:196 +0x65
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0007440d0, {0xc000742100, 0x2, 0x2})
go.uber.org/[email protected]/zapcore/entry.go:262 +0x3ec
go.uber.org/zap.(*Logger).Panic(0x10da0a2?, {0x10e7885?, 0xf19800?}, {0xc000742100, 0x2, 0x2})
go.uber.org/[email protected]/logger.go:284 +0x59
go.etcd.io/etcd/pkg/v3/schedule.(*fifo).executeJob.func1()
go.etcd.io/etcd/pkg/[email protected]/schedule/schedule.go:202 +0x2cb
panic({0xf19800, 0xc00072c0b0})
runtime/panic.go:884 +0x213
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x2?, 0x7fbfdbc7f0e8?, {0x0?, 0x0?, 0xc00008c1c0?})
go.uber.org/[email protected]/zapcore/entry.go:196 +0x65
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc000744000, {0xc000742000, 0x2, 0x2})
go.uber.org/[email protected]/zapcore/entry.go:262 +0x3ec
go.uber.org/zap.(*Logger).Panic(0xc000324150?, {0x10ff498?, 0xc?}, {0xc000742000, 0x2, 0x2})
go.uber.org/[email protected]/logger.go:284 +0x59
go.etcd.io/etcd/server/v3/etcdserver/api/membership.mustDeleteMemberFromStore(0xc0003241f8?, {0x128b4f8, 0xc000324150}, 0xc0006f1120?)
go.etcd.io/etcd/server/v3/etcdserver/api/membership/storev2.go:104 +0x25c
go.etcd.io/etcd/server/v3/etcdserver/api/membership.(*RaftCluster).RemoveMember(0xc0003241c0, 0x1279b60?, 0x0)
go.etcd.io/etcd/server/v3/etcdserver/api/membership/cluster.go:436 +0xd8
go.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).applyConfChange(0xc0007ad500, {0x1, 0x1, {0x0, 0x0, 0x0}, 0xd7588c01e226ed05}, 0xc000488d80, 0x0)
go.etcd.io/etcd/server/v3/etcdserver/server.go:2039 +0x27a
go.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).apply(0xc0007ad500, {0xc0005c2c90, 0x5, 0x0?}, 0x0?, 0xc000596420)
go.etcd.io/etcd/server/v3/etcdserver/server.go:1844 +0x536
go.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).applyEntries(0xc0007ad500, 0xc000488d80, 0xc000000000?)
go.etcd.io/etcd/server/v3/etcdserver/server.go:1131 +0x26b
go.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).applyAll(0xc0007ad500, 0xc000488d80, 0xc000000000)
go.etcd.io/etcd/server/v3/etcdserver/server.go:919 +0x65
go.etcd.io/etcd/server/v3/etcdserver.(*EtcdServer).run.func8({0xc0000980b8, 0xc000596240})
go.etcd.io/etcd/server/v3/etcdserver/server.go:842 +0x25
go.etcd.io/etcd/pkg/v3/schedule.job.Do(...)
go.etcd.io/etcd/pkg/[email protected]/schedule/schedule.go:41
go.etcd.io/etcd/pkg/v3/schedule.(*fifo).executeJob(0xc00056b790?, {0x1279ae8?, 0xc0000101c8?}, 0x0?)
go.etcd.io/etcd/pkg/[email protected]/schedule/schedule.go:206 +0x88
go.etcd.io/etcd/pkg/v3/schedule.(*fifo).run(0xc0007b81c0)
go.etcd.io/etcd/pkg/[email protected]/schedule/schedule.go:187 +0x11a
created by go.etcd.io/etcd/pkg/v3/schedule.NewFIFOScheduler
go.etcd.io/etcd/pkg/[email protected]/schedule/schedule.go:101 +0x18b
Test: TestRemoveNonExistingMember
logger.go:130: 2023-11-24T23:10:47.683+0800 INFO closing test cluster...
logger.go:130: 2023-11-24T23:10:47.683+0800 INFO closing server... {"name": "TestRemoveNonExistingMember-test-0"}
logger.go:130: 2023-11-24T23:10:47.683+0800 INFO removing directory {"data-dir": "/tmp/TestRemoveNonExistingMember3670107214/002"}
logger.go:130: 2023-11-24T23:10:47.683+0800 INFO closed test cluster.
--- FAIL: TestRemoveNonExistingMember (0.17s)
ahrtr
approved these changes
Nov 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This simple test shows that approach presented in #16084 to just switch validation to just use v3 store is incorrect
If run on top of the PR it results in panic
Issue is cause by skipping validation of entries from last snapshot.