I think this is a bug.
I’m using Octopus Deploy 18.104.22.1683, with tencales in listening mode. When I create and deploy a release using Octo.exe to an environment not containing any instances of a particular targeted role, I get an fatal error in the acquire packages stage - rather than just a warning.
The error relating to a package that has no associated machines in the role is:
“When comparing the hashes of the packages downloaded by each machine, one or more machines returned a different hash for the package. Deployment will not proceed since this would result in inconsistencies between the files installed on different machines.”
When using the UI it prevents me from getting into this scenario and marks the steps with missing machines in those roles as skipped. When triggering a deployment I would expect it to just ignore steps if there are no associated machines even if not set to skip (I beleive this is the behaviour in 1.0?).