All my tentacles show as offline after upgrade to 3.2.15.
Can you please assist?
THIS IS REALLY BAD GUYS…
I thought I wanted to upgrade from 3.2.14 to avoid tentacle communication issues as you said, and now that I upgraded to 3.2.15 I have tentacle communication issues!
I cannot physically go an manually update tentacles to version 3.2.15 across all our environments now. Always depended on Octopus server to do that via the Environments page.
Tried to look and reinstall server 3.2.14 but the download link has been removed. Does that mean, the only option I have now is to further downgrade to 3.2.13!?
Please advice ASAP!
I reverted the Octopus server to 3.2.13 and restarted the machine and I’m still having the issue.
OMG
Seriously, not even going to server 3.2.13 will work?
All my tentacles are now 3.2.14.
How am I supposed to get this this fixed.
Guys, PLEASE MAKE THE DOWNLOAD LINK FOR 3.2.14 AVAILABLE!
Hi,
I’m very sorry to hear you guys are facing these issues. 3.2.14 introduced an incompatibility that prevented 3.2.14 Tentacles to talk to any server besides 3.2.14. For this reason we pulled off 3.2.14 as soon as possible, to avoid spreading that version across many user’s Tentacles.
The workaround for the scenario of "I have all my Tentacles in 3.2.14 and upgraded my Octopus server to 3.2.15 " are:
A) Manually/script upgrade your Tentacles to 3.2.15.
B) Downgrade your Octopus server to 3.2.14 using the MSI installer on the link below. This is only to make you productive once again in the short term. An upgrade to 3.2.15 will have to be planned.
https://drive.google.com/folderview?id=0B9ntXdSzeVC6UUNtZXVsREhZbTg&usp=sharing
Once again, I apologize on behalf of the team for the inconvenience. We pulled that bad build as soon as we could to avoid spreading this issue, but unfortunately there were very few cases like yours who were affected by it.
Please keep me posted on your progress with either of the above solutions.
Regards,
Dalmiro
Av (sorry I dont know your name) - Can you confirm which version are your Tentacles running? I just want to make sure you have the Tentacles on 3.2.14 and the server on a different version so you can follow the instructions of my previous reply.
Fernando - You should be able to follow approaches A or B.
Please keep me posted
Tentacles are on 3.2.14.
Av - You should be able to follow approaches A and B of my previous reply.
Dalmiro, your first method worked. Thanks. Will you be coming out with a patch (3.2.16 ?) so that I don’t have to manually fix all the tentacles?
Av - If you were able to follow approach A, meaning you upgraded your Tentacles manually/script to 3.2.15, then you wont have any problems upgrading to future versions. The “patch” for this issue is in 3.2.15
I don’t want to have to manually upgrade all tentacles from 14 to 15. Is there another way to do that?
Or do you at least have a script that will do the upgrade including downloading http://octopusdeploy.com/downloads/latest/OctopusTentacle64, running it, and upgrading all tentacles (there may be multiple on the machine).
Av - Unfortunately we don’t have a script to automate this task. Since the Tentacles cannot connect to the Octopus Server, other means to connect to the boxes running the Tentacles will have to be used for the upgrade (preferably PS remoting). There are just too many environmental things that could break a script made by us if we write one.
How Many machines running Tentacles do you have roughly? If they are too many and a manual upgrade is not viable, I’d recommend you to try to use the Tentacle Chocolatey package to automate the download & install process. If you have more than one Tentacle instance on a machine, only running the MSI to upgrade once will upgrade all the instances.
Thanks, Dalmiro!
We use a script similar to the below to install a new Tentacle. Is it the
same syntax when doing an upgrade?
$installer = "$env:UserProfile\desktop\Octopus.Tentacle.x-x64.msi"
wget “http://octopusdeploy.com/downloads/latest/OctopusTentacle64” -OutFile
$installer
msiexec /i $installer /quiet
$apiKey = “API-zzz”
$role = “”
$environment = “”
$server = “http://zzz:port”
$instance = “Tentacle” #that’s the default name for one instance.
$name = “$env:computername”
$serverThumbprint = “”
$port = 10933
cd “C:\Program Files\Octopus Deploy\Tentacle” #rem we need to add " (x86)"
on 32-bit machines…
Tentacle.exe service --instance “$instance” --stop --uninstall
Tentacle.exe delete-instance --instance “$instance”
Tentacle.exe create-instance --instance “$instance” --config
"C:\Octopus\Tentacle.config" --console
Tentacle.exe new-certificate --instance “$instance” --if-blank --console
Tentacle.exe configure --instance “$instance” --reset-trust --console
Tentacle.exe configure --instance “$instance” --home “C:\Octopus” --app
"C:\Octopus\Applications" --port “$port” --console
Tentacle.exe configure --instance “$instance” --trust “$serverThumbprint”
–console
"netsh" advfirewall firewall add rule “name=Octopus Deploy Tentacle” dir=in
action=allow protocol=TCP localport=$port
Tentacle.exe register-with --instance “$instance” --name “$name” --server
"$server" --apiKey “$apiKey” --role “$role” --environment “$environment”
–comms-style TentaclePassive --console
Tentacle.exe service --instance “$instance” --install --start --console
Avraham Y. Seff
Hi Avraham,
It should be only this part of the code:
$installer = "$env:UserProfile\desktop\Octopus.Tentacle.x-x64.msi"
wget "http://octopusdeploy.com/downloads/latest/OctopusTentacle64" -OutFile $installer
msiexec /i $installer /quiet
I just tried it on a test VM and it worked. The only thing left here would be to wrap that code around a remote execution cmdlet like invoke-command with the -computername parameter. Otherwise manually running that command on each machine should work.
Awesome. Thanks!
Same issue here. Had to login to every server and reinstall the tentacle. To add insult to inury, Calamari needed updating too. Fortunately the latter was doable from the web interface.
Hoping that future releases don’t have such issues!
Dalmiro, as a result of deleting and reinstalling tentacles I lost all variables for those settings. How can I get them back?
Av - All that was needed was to upgrade the 3.2.14 Tentacles using the MSI. There was no need to delete the Tentacles from Octopus. I’m afraid that now that the Tentacles have been deleted, their IDs are now invalid, along with all the variables scopes that depended on them.
The only way would be to manually set the scopes once again pointing to the new Tentacles.