Attempting to deploy to 100’s or 1000’s of remote nodes at a time and seeing the errors below from Octopus Deploy. This issue is now a show stopper for our company’s use of OD.
Scenario is during a Deploy a Package step doing the Acquire operation one (or more) nodes connection is lost OR even when one or more nodes are unavailable in an environment, which is a possible normal occurrence when deploying to 100’s of remote locations across North America and around the world. So see the typical message in the log:
“after the request began: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.”
Then during the actual install attempting to run Pre-Deploy and Deploy scripts a node that failed connectivity during the Acquire package operation reports the following exception in the logs:
No package for the action ‘51ec4296-5e21-41fd-b70c-19c395fbfded’ and machine ‘Machines-2708’ was acquired.
at Octopus.Core.Model.Projects.AcquiredPackageMap.GetPackageForMachine(String actionId, String machineId) …
After that every node just fails without any error and just see this in the logs:
This error make Octopus Deploy unusable for our needs to deploy to 100’s to 1000’s of remote nodes.