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

If $install_method = 'url', won't upgrade consul #103

Closed
EvanKrall opened this issue Apr 12, 2015 · 2 comments
Closed

If $install_method = 'url', won't upgrade consul #103

EvanKrall opened this issue Apr 12, 2015 · 2 comments

Comments

@EvanKrall
Copy link
Contributor

I have to manually remove both /usr/local/bin/consul and /opt/staging/consul/consul.zip to get this module to upgrade Consul.

@hopperd
Copy link
Contributor

hopperd commented Apr 13, 2015

Yea this one has to do with the filename that is being set with the staging module. It is writing it to consul.zip as you see. Same goes for the UI as well.

Given the upgrade instructions by Consul:

  1. On each server, install version B of Consul.
  2. Shut down version A, restart with version B.
  3. Once all the servers are upgraded, begin a rollout of clients following the same process.
  4. Done! You are now running the latest Consul agent. You can verify this by running consul members to make sure all members have the latest build and highest protocol version.

We'd probably need to detect that an upgrade was happening before automatically replacing the binary (though that would still probably work to just replace and issue a restart)

gozer added a commit to gozer/nubis-consul that referenced this issue May 25, 2015
@hopperd
Copy link
Contributor

hopperd commented Dec 15, 2015

This should now be resolved via #202

@hopperd hopperd closed this as completed Dec 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants