After upgrading our server to
3.4.12, we are now unable to deploy any of our existing projects that include an Azure Web App.
| == Failed: Step 29: Deploy Web Hooks to Production SaaS ==
04:06:29 Fatal | The step failed: Activity Deploy Web Hooks to Production SaaS on SaaS Services 1 failed with error 'No package for the action 'faea26e5-0066-45ec-8720-9d0447163714' on the server was acquired.'.
04:06:29 Verbose | Deploy Web Hooks to Production SaaS completed
We’ve look into the following but unable to find any suitable fix/workarounds :
Any help will be greatly appreciated.
Thanks for getting in touch.
The issue you linked happens when the web app step is scoped to a role and there are Tentacles that have that role. The package will be acquired by the Tentacle but not by the Octopus Server so the web app step fails.
If that sounds like the issue you are experiencing, we are currently working on a fix and will have it out in the next release (shortly). A workaround would be to ensure there are no Tentacles with the role that the web app step is deploying to.
If that doesn’t sound like what you are experiencing, would you mind sending your full task log? (Instructions: http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task)
Thanks for the quick reply, yes it’s seem to be the issue where the web app is scoped to a role and we have tentacle that have that role.
Glad to hear about the fix. Will be looking forward to it.
This issue has now been fixed as at release version 3.4.13.