Octopus Server Version Number: 4.1.1
Hello!
Steps to Reproduce
- Have a Tentacle with a particular name that’s fully configured (installed on a machine to deploy to, recognized and healthy from the vantage point of the Octopus Server, etc.).
- Install a new Tentacle on a separate machine using the same name as the existing Tentacle.
- After setup is complete, the first Tentacle will seemingly no longer exist in the eyes of the Octopus Server; it seems to have been overwritten by the new Tentacle of the same name.
I would have expected the Octopus Server to validate that the Tentacle name is not a duplicate during Tentacle installation and prompt for a unique value. Right now it silently allows the Tentacle with the duplicate name to be created and the first Tentacle becomes toast, so you don’t even know you’re effectively performing a delete operation on existing infrastructure and screwing things up. It can be magnified further in that the default value for Tentacle names during installation is the computer’s machine name, and some cases such machines can have fairly generic names that would be duplicates.
We ran into this issue in production that now requires working with a client to reconfigure their Tentacle before we are able to deploy to them again. Reinstalling a Tentacle is even more effort when you’ve lost the Environments, Tenants, or other configuration on the Tentacle that needs to be correctly restored.
Our workaround is that before we install any new Tentacles we need to manually look in Octopus to see if there are any existing Deployment Targets of the same name, but there is room for error in doing this.
I tried searching for this as an existing issue and the best things I could find were two comments (this one and this one) in the same thread that were posted by Robert Wagner.
Still, thank you for all the hard work and for creating such a great product!
Kevin