Deployments failing

Legacy Uncategorised
1

Okay - running version 3.2.14
Tried upgrading to the latest version, ran into the bug about then tentacles not being able to communicate, so I reinstalled version 3.2.14, restarted the server, then ran the health check on all the tentacles and all came back okay, until I tried to deploy a test project…

It quite happily pushed the package to the test server, then when I asked it to run the second step, to create an IIS Application using the step from the library it fails.

The log reports the following

Executing script on ‘GBBED13WS04V’

11:56:48

Info
--------------PS Script Starting----------------

11:56:48

Error
Get-Content : Cannot find path ‘D:\Bootstrap.ps1’ because it does not exist.

11:56:48

Error
At D:\Scripts\invokesql.psm1:23 char:23

11:56:48

Error

  •     $Query = Get-Content <<<<  $InputFile

11:56:48

Error
+ CategoryInfo : ObjectNotFound: (D:\Bootstrap.ps1:String) [Get-C

11:56:48

Error
ontent], ItemNotFoundException

11:56:48

Error
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo

11:56:48

Error
ntentCommand

11:56:48

Error

11:56:49

Fatal

The first script it mentions does not exist - the second one does, but shouldn’t be called from this.
Help!

2

Hi,

Thanks for reaching out. I’m very sorry to hear you were bitten by the 3.2.14 bug. We pulled that version off as soon as we noticed the problem, but some early adopters of our versions were too fast even for us :frowning:

Could you please follow these steps to provide us a full deployment log?

  1. Add these 2 variables to your project http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables

  2. Create a new release (so the new variables take effect) and deploy it. If possible skip as many steps as you can and only leave step we are troubleshooting in order to avoid the noise in the log.

  3. Send us the raw log of that deployment http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task

Regards,
Dalmiro

3

Hi Dalmiro,

Seems to be working now. Looks like there was a server reboot, combined with removing unnecessary script modules. That seems to have resolved the issue.

Now all we need to do is plan our upgrade to 3.2.20. Any tips on how to make that as smooth as possible?

Emma

4

Hi Emma,

Check this comment on another similar thread: http://help.octopusdeploy.com/discussions/problems/43975-upgrade-to-3217-broke-all-tentacles#comment_38946595

You should be already on step 2 since your Tentacles and Server are in 3.2.14 and talking to each other successfully. So start from step 3.

Let me know how that goes
Dalmiro