We had machines that IT defined as part of environment but they weren’t used yet in any deployment steps. Snapshot restore on one of those put it under old tentacle version, but since we didn’t use it yet - didn’t care. Once our automated deployment ran through, it failed because one of the machines in environment isn’t running current tentacle version. Should deployment process that doesn’t use that machine be kicking off anyway?
Thanks for getting in touch! What version are you running? We fixed this issue in 2.5.9.
Hope that helps!
Octopus Deploy 184.108.40.2066 - and I’m still having this problem.
Could you please provide the following screenshots:
Your project process, the environment this is occurring in, and the deployment screen where the error shows.
I need to try to replicate it.
By looking things over carefully, this may be of interest:
I have 2 environments, staging and production
In staging, there is that reverted-not-used VM called CACHE1 with role
My process includes a step for CACHE role but it’s for production ONLY.
I was trying to trigger deployment for staging and that’s where it wasn’t
allowing me to proceed.
Error message was showing up on this screen before I disabled that machine.
[image: Inline image 2]
I will have a go at replicating this, but the workaround should be to disable that machine (edit the machine and disable).
I will update the thread when I create an issue with my findings.
I have confirmed that in 3.0 Tentacles won’t require to be upgraded as the process is changed, so this situation will not happen.
So this bug is considered fixed in 3.0.