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

Refuse to choose among multiple candidates for IP address #1099

Closed
mfischer-zd opened this issue Jul 9, 2015 · 1 comment
Closed

Refuse to choose among multiple candidates for IP address #1099

mfischer-zd opened this issue Jul 9, 2015 · 1 comment
Labels
type/enhancement Proposed improvement or new feature

Comments

@mfischer-zd
Copy link
Contributor

On complex hosts, there may be more than one valid (non-loopback) IP address that Consul could choose to present to the cluster for inter-node communication. Consul should refuse to automatically select one in this situation, because it could pollute the cluster information with a non-routable or otherwise incorrect IP address for that node if it guesses wrong.
@ryanuber ryanuber added the type/enhancement Proposed improvement or new feature label Jul 13, 2015
@ryanuber
Copy link
Member

Thanks for the suggestion, and agreed!

@armon armon closed this as completed in 182f881 Jul 23, 2015
armon added a commit that referenced this issue Jul 23, 2015
@armon
Merge pull request #1119 from trumant/multiple_private_IPs
dcb5ae7 
Fixes #1099 by raising an error when we multiple private IPs are found
@bborysenko bborysenko mentioned this issue Jul 21, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mfischer-zd @ryanuber