We are running Octopus Deploy 3.4.5 and use Triggers to initiate deployment to new tentacles in AWS. We use Artifactory Professional 4.13.2 rev 40285.
We periodically receive the following error with trigger initiated deployments:
The step failed: Activities failed with errors XYZ.Web on i-036aea16: ‘No package for the action ‘04e16b78-65c8-4f46-b7f1-551ed8e398ff’ and machine ‘Machines-1016’ was acquired.’
When this happens it happens for all packages, and all machines that are involved in that deployment.
Thanks Shane. Attached is what looks like a fully successful deploy.
FYI - have raised a seperate ticket just now about a problem with auto
deploy skipping a step that it shouldn’t. Probably not related but perhaps
something you can also help with?
I’ve been able to reproduce both of the issues you are seeing, both bugs we will fix shortly.
It looks like automatic deployments are running steps that were manually skipped during the initial deployment which is causing the package acquisition error.
The steps that aren’t run I believe is because the steps are scoped to multiple roles.