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.

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

consul client address configs are not parseable via go-socketaddr #3322

Closed
preetapan opened this issue Jul 25, 2017 · 1 comment
Closed

consul client address configs are not parseable via go-socketaddr #3322

preetapan opened this issue Jul 25, 2017 · 1 comment
Assignees
Labels
type/bug Feature does not function as expected

Comments

@preetapan
Copy link
Contributor

preetapan commented Jul 25, 2017

$docker run --name=dev-consul consul agent -dev -client='{{ GetInterfaceIP "eth0" }}'
==> Starting Consul agent...
==> Error creating agent: Invalid DNS bind address: Failed to parse IP: {{ GetInterfaceIP "eth0" }}

looks like we don't use the go-socketaddr library to parse this arg. We do for bind addr. This should be consistent for both.

@preetapan preetapan added the type/bug Feature does not function as expected label Jul 25, 2017
@gwydirsam
Copy link

We ran into something similar --

==> WARNING: Expect Mode enabled, expecting 3 servers
==> Starting Consul agent...
==> Error creating agent: Invalid DNS bind address: Failed to parse IP: {{GetPrivateIP}}

The error checking here is being run before the templates are resolved here

@preetapan preetapan self-assigned this Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

2 participants