You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
On each server, install version B of Consul.
Shut down version A, restart with version B.
Once all the servers are upgraded, begin a rollout of clients following the same process.
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
I have to manually remove both /usr/local/bin/consul and /opt/staging/consul/consul.zip to get this module to upgrade Consul.
The text was updated successfully, but these errors were encountered: