Installation of packages is randomly skipped on packages that have not yet been installed

Legacy Uncategorised
1

Since upgrading to 3.4 we started to randomly see Octopus Deploy randomly skip packages that it thinks are installed when they haven’t been.
For the project, I do have skip packages that are already installed turned on.

Here is it uploading the package:
Upload package Browse version 3.13.2.10122
September 1st 2016 05:35:52
Info
Found matching version 3.13.1.10120: D:\Octopus\OctopusServer\PackageCache\feeds-internalpackages\Browse.3.13.1.10120_221BA426710E6143B9DFEE4E4377CB1A.nupkg
September 1st 2016 05:35:55
Info
Package Browse version 3.13.2.10122 successfully uploaded to this server
Building delta for Browse version 3.13.2.10122
September 1st 2016 05:35:52
Info
Using package D:\Octopus\OctopusServer\PackageCache\feeds-internalpackages\Browse.3.13.1.10120_221BA426710E6143B9DFEE4E4377CB1A.nupkg with hash acce2a777cae982d1905d958a358a4b6a7beb862 for creating delta
September 1st 2016 05:35:52
Info
Original package was 31 MB, delta file is 2 MB
Uploading and applying delta Browse.3.13.1.10120_to_3.13.2.10122.octodelta
September 1st 2016 05:35:54
Info
Applying delta to D:\Octopus\Files\Browse.3.13.1.10120.nupkg-1e1a5b88-f33a-467e-8aa1-43c6cbb085c9 with hash acce2a777cae982d1905d958a358a4b6a7beb862 and storing as D:\Octopus\Files\Browse.3.13.2.10122.nupkg-3bdf7891-19b0-4628-a193-1b158b8c4177
September 1st 2016 05:35:54
Info
Applying delta: 0%
September 1st 2016 05:35:54
Info
Applying delta: 70%
September 1st 2016 05:35:54
Info
Applying delta: 90%

Here is it skipping the step:
Deploy Browse
September 1st 2016 05:38:04
Verbose
Octopus Server version: 3.4.0+Branch.master.Sha.
September 1st 2016 05:38:04
Info
Deploying package ‘D:\Octopus\Files\Browse.3.13.2.10122.nupkg-bf5a2a77-9df6-4844-9b59-466a3d47ccc5’ to machine 'https://webserver1:10933/'
September 1st 2016 05:38:06
Verbose
Octopus Deploy: Calamari version 3.4.0+Branch.master.Sha.
September 1st 2016 05:38:06
Info
Deploying package: D:\Octopus\Files\Browse.3.13.2.10122.nupkg-bf5a2a77-9df6-4844-9b59-466a3d47ccc5
September 1st 2016 05:38:06
Info
The package has already been installed on this machine, so installation will be skipped.

2

If you’re deploying the same package to the same machine/tentacle on different paths - then that’s the problem.

I have the same issue and reported it at http://help.octopusdeploy.com/discussions/problems/47310-deploying-the-same-package-to-multiple-paths-on-the-same-tenant-using-multiple-steps.

3

Hi Peter,

To assist us in troubleshooting this issue, could you please send through the full log of a deployment that is experiencing this issue please?

Thank you and best regards,
Henrik

4

This is an actual issue I have as well.
Making a new release with new packages (different version number and name), only the first one will be deployed, subsequent packages will be skipped even though this version is not deployed as it is brand new.

I don’t have the issue in an another project, differences I can find is that I am using #{Octopus.Action.Package.PackageId}.exe for the Executable Path in all the steps in the failing project (explicitly stated in the working one).

5

Hi Thibault,

Could you also send through the full log of a deployment that experienced this issue, I’ve tried to replicate the issue locally but have not been able to reproduce it (yet).

Thank you,
Henrik

6

Here is the full deployment log, as well as a screenshot of the server directory listing for one of the package I am deploying.

ServerTasks-22828.log.txt (145 KB)

fwqfqwfqwf.png

7

Hi Thibault,

Looking through the logs, I can’t really see any reason for why it would be skipping the other steps, so I’ll ask for some more information.

Are the package steps setup to run in parallel? And, could you send through the DeploymentJournal.xml from CBISTEST01, as there could be some corrupt data in there that is causing the issue.

Also, if you could add this variable OctopusPrintEvaluatedVariables with a value of true (you’ll need to create a new release after adding the variable) and send me the deployment log with this issue happening, this will give me what variables are available and that could also assist with troubleshooting this issue.

My apologies for the inconvenience caused by this issue.

Thank you,
Henrik

8

Yes, all the packages steps are parallels.
Here are the files.

DeploymentJournal.xml (316 KB)

ServerTasks-22925.log.txt (3 MB)

9

Hi Thibault,

After further investigation, this looks to have been a bug in 3.4.0 where the deployment entries in the DeploymentJournal.xml file for all but the first step are created incorrectly with a blank PackageId and PackageVersion. If you upgrade your Octopus Server to 3.4.4 or later, this should be rectified.

I hope that helps!

Thank you,
Henrik

10

The update fixed the bug, thank you!

11

Hi Thibault,

Great to hear, thanks for letting me know!

Happy deployments!

Thank you and warm regards,
Henrik

12

Notice:

This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.