search

cloudfoundry-attic / consul-release

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

Upgraded to 181 and need way to "refresh" node-name #81

Open andrew-edgar opened 7 years ago

andrew-edgar commented 7 years ago

The code in confab preserves the old "node-name" no matter what. As long as node-name.json exists the old node-name will be used.

We have a use case where we have already deployed things but want to change all the nodes to use "node_name_include_id: true" property.

We deployed an updated version of consul release but since the node-name.json always existed it never changed to use the correct more unique node name.

We had to do some weird processing to delete the node-name.json prior to doing the update but this is not repeatable.

We would like a property that could be set which will cause the node name to be regenerated. If there is another way to do this in a single bosh deploy please let us know as this would be required on the upgrade but not on a normal restart of consul.

cf-gitbot commented 7 years ago

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

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

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

mcwumbly commented 6 years ago

we ran into the same issue today and ended up doing a bosh recreate to work around it. thankfully, we don't anticipate having to change this value very often.