I was using the Apply Terraform step in a project.
In the step itself I had selected the option to ‘Run on the Octopus server’. But I has also moved this group to be grouped with a Slack notification step. Doing so meant I had to apply a deployment role at the parent step level. The role I applied ‘octopus-server’ contains only the Octopus server itself.
When the Apply terraform step ran, this error immediately occurred:
The step failed: Activity Apply Terraform on OCTOSERVER01 failed with error ‘No package for the action ‘96995048-4e5e-46ac-89ff-cfc05f6e0ae5’ on the server was acquired.’.
The release was correctly created with a valid package from the feed.
When I removed the parent step, removed the role scoping for the Apply Terraform step (and let it remain on the Slack notification step, everything works again. I am certain this has to do with the role scoping.