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

new version management node should refuse old version MN #145

Open
youyk opened this issue Oct 26, 2015 · 1 comment
Open

new version management node should refuse old version MN #145

youyk opened this issue Oct 26, 2015 · 1 comment
Labels
bug

Comments

@youyk
Copy link
Contributor

youyk commented Oct 26, 2015

When there are 2 management nodes, after upgrading the 1st management node with database, the 2nd management node is still old version. In this situation, the upgraded 1st management node should refuse 2nd management node to join the service.
@youyk youyk added the bug label Oct 26, 2015
@youyk youyk added this to the 1.0 milestone Oct 26, 2015
@zxwing zxwing removed this from the 1.0 milestone Dec 27, 2015
@zxwing
Copy link
Contributor

zxwing commented Dec 27, 2015

this needs a fair amount of work; move it to milestones after 1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zxwing @youyk