search

cloudfoundry-attic / consul-release

This is a BOSH release for consul.
Apache License 2.0
10 stars 30 forks source link

Consul fails to start when dynamic networking on SoftLayer #32

Closed andrew-edgar closed 8 years ago

andrew-edgar commented 8 years ago

With the change introduced with CF 238 and the commit specified here ... https://github.com/cloudfoundry-incubator/consul-release/commit/55cb4a414c687d0ec91a5ac9d2358aec5fe7d930#diff-25ba660257040d54208c35f5397fb084

The external_ip is filled in as a FQDN instead of an IP address. When deployed on SoftLayer with dynamic networking.

The memberlist.go calls net.ParseIP which expects an IP address.

The bosh team said they are looking at adding spec.ip for cases where an IP address is required. But that spec.address does NOT guarantee an IP address.

cf-gitbot commented 8 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/126793339

The labels on this github issue will be updated when the story is started.

Amit-PivotalLabs commented 8 years ago

Thank @andrew-edgar. When you say that the BOSH team is looking into spec.ip, do you know what the ETA for that is?

We switched from our custom IP discovery function to the BOSH-provided spec.address under the expectation that it would do the same thing, but seems like it's actually not suitable for all networks. I thought I remember @cppforlife saying that in the case of dynamic networks, BOSH would stall plan to provide a correct value for spec.address by rendering the template after the VM had been provisioned.

/cc @cppforlife @sykesm