-
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
e2e: mismatched etcd versions for rolling upgrades #5697
Labels
Milestone
Comments
This is good. We only do once, right before the release. It would be great if we do this for every e2e test runs, going forward with v3 releases. |
gyuho
added a commit
to gyuho/etcd
that referenced
this issue
Jul 9, 2016
gyuho
added a commit
to gyuho/etcd
that referenced
this issue
Jul 9, 2016
For etcd-io#5697. ``` MIGRATION_FROM=v3.0.2 go test -v -run TestReleaseMigrate ```
gyuho
added a commit
to gyuho/etcd
that referenced
this issue
Jul 9, 2016
For etcd-io#5697. ``` MIGRATION_FROM=v3.0.2 go test -v -run TestReleaseMigrate ```
gyuho
added a commit
to gyuho/etcd
that referenced
this issue
Jul 9, 2016
gyuho
added a commit
to gyuho/etcd
that referenced
this issue
Jul 9, 2016
closed by #5697 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Partially in response to #5696, where a missing field from an older version crashes the newer etcd. Right now there's no infrastructure for testing configurations with mismatched etcd server versions.
This case could be covered to some extent by having all e2e tests with more than one member run (either by default or some configuration option) some members on the last stable release and the rest on the current branch.
The text was updated successfully, but these errors were encountered: