I am currently in the middle of an upgrade from 2.6 -> 3.0. I tried to upgrade the tentacles using the Hydra package. It worked on a few machines, but on the majority, it failed silently. It looks like the package got installed, but the old tentacle didn’t get replaced. So the bits for 3.0 are installed, but the service is still pointing to the 2.6 version. I have done the update manually in the meantime, but I wanted to let you know. It may be because the 2.6 Tentacles were installed to a different drive?
Hi,
What version of the Hydra package are you using? We did find an issue when Tentacles had been updated using Octopus previously, we had to account for this and update the service path. This was released very recently.
The different drive path might be a new issue. Are you able to please send the Hydra logs from one that failed so we can try to figure it out? http://docs.octopusdeploy.com/display/OD/Troubleshooting
Thanks!
Vanessa
It was version 3.0.6.2130.
I will try to take a look later at getting logs, but at the moment I just want to get the rest of it up and running.
Hi,
I’m having the same problem. I did an upgrade from 2.6 to 3.0.9 on one of our Octopus servers today. This is a small environment with only 7 tentacles so I’m doing this one before the large production server with a 100+ tentacles.
I used version 3.0.6.2130 of Hydra since this is referenced in the documentation http://docs.octopusdeploy.com/pages/viewpage.action?pageId=3048133 and seem to be the only version available.
The new tentacle version was installed fine on all tentacles, but the service was still pointing to the old 2.6 binaries. I had to manually RDP into each server and run ReInstall from the Octopus Tentacle Manager to fix the issue. No errors was logged in the hydra log.
This will not work on our large Octopus installation. We really want to upgrade to Octopus 3 asap, but this issue is blocking the upgrade.
Any news on fixing this issue?
/Jan
Hi Jan,
We have updated the Hydra package just today (link updated in the documentation), it now references the new Tentacle location for a reinstall and should correctly point the service to the new Tentacle binaries.
Please let me know how this goes.
Vanessa
Hi Jan,
Just to clarify (in case you got there really early!) the fix is in version 3.0.10 of the Hydra package.
I’m looking forward to hearing how it goes!
Damo
Thanks. I’ll test it soon
/Jan