Chain Deployment GET projects Call Fails

[Tyson_Knutson]

I am getting errors when trying to trigger a chain deployment:

Here is a snippet of the log located at C:\Octopus\Logs:
2018-11-12 13:05:30.3279 820 1 INFO ================================================================================
2018-11-12 13:05:30.3279 820 1 INFO Changed log folder from C:\Windows\system32\config\systemprofile\AppData\Local\Octopus\Logs to C:\Octopus\Logs
2018-11-12 13:05:30.3279 820 1 INFO Tentacle.exe version 3.20.1 (3.20.1+Branch.master.Sha.ef04cf3c1ae85945d26c7e30dcacb31daff01ea5) instance Tentacle
2018-11-12 13:05:30.3279 820 1 INFO Environment Information:
OperatingSystem: Microsoft Windows NT 6.3.9600.0
OsBitVersion: x64
Is64BitProcess: True
CurrentUser: NT AUTHORITY\SYSTEM
MachineName: LABW6412HVM034
ProcessorCount: 4
CurrentDirectory: C:\Windows\system32
TempDirectory: C:\Windows\TEMP
HostProcessName: Tentacle
PID: 820
2018-11-12 13:05:30.4060 820 1 INFO ==== CheckServicesCommand ====
2018-11-12 13:05:30.4217 820 1 INFO CommandLine: C:\Program Files\Octopus Deploy\Tentacle\Tentacle.exe checkservices --instances * --console --nologo
2018-11-12 13:06:01.8677 1268 13 INFO listen://[::]:10933/ 13 Accepted TCP client: [::ffff:10.156.80.47]:63002
2018-11-12 13:06:01.8677 1268 13 INFO listen://[::]:10933/ 13 Performing TLS server handshake
2018-11-12 13:06:01.8832 1268 13 INFO listen://[::]:10933/ 13 Secure connection established, client is not yet authenticated, client connected with Tls12
2018-11-12 13:06:01.8989 1268 13 INFO listen://[::]:10933/ 13 Client at [::ffff:10.156.80.47]:63002 authenticated as D883475DA39AAE738E9B17CCD84583258DF61B9E
2018-11-12 13:06:01.9457 1268 14 INFO [ServerTasks-150786] [RunningScript] [Read Lock] [no locks] Trying to acquire lock.
2018-11-12 13:06:01.9457 1268 14 INFO [ServerTasks-150786] [RunningScript] [Read Lock] [“ServerTasks-150786” (has a read lock)] Lock taken.
2018-11-12 13:06:03.0082 1268 14 INFO [ServerTasks-150786] [RunningScript] [Read Lock] [“ServerTasks-150786” (has a read lock)] Releasing lock.

Other OD projects are using this step successfully. Of course, those projects use different Deployment Targets.

What may be the issue with the deployment target that I am attempting to use? Or is it possibly an API key issue?

Here is the status of the target:

TIA.

[distantcam (Cameron MacFarland)]

Hi Tyson,

Thanks for contacting us. It looks like the tentacle is having trouble connecting to the server in order to do the chain deployment.

The easiest way to check this is to see if you can access https://serveraddress/api from the tentacle. Also check the firewall to see if the tentacle can reach the server on https.

Also, I noticed the step is running on the tentacle. Instead if you run the step on the server there shouldn’t be a connection issue.

Hope that helps.

[Tyson_Knutson]

Thank you for the suggestions, I will look into them.

As for running on the server, I would but it has version 4 of Powershell, so I cannot. And I am told that we cannot upgrade it for some reason. But I’ll ask again.