We have deployment environments with Azure VMs (or scale sets). Each Azure VM has Tentacle installed and shows up in the environment as deployment target. Unfortunately about once a week we observe deployment targets become unhealthy and looking deeper we can see that some tentacles change their thumbprint comparing to what they were registered with and therefore fail communication check. Manual re-registering tentacle with its new thumbprint makes it healthy again.
The question is What could make tentacles change their registration thumbprint?
Thanks for getting in touch! I’m sorry to hear you’re hitting this confusing behavior. I suspect this may be caused by something within the DSC template you may be using. Would you be willing to provide the Tentacle logs (located in C:\Octopus\Logs in standard installations) to shed more light on this?
I look forward to hearing back and getting to the bottom of this one!
Thank you, Kenny!
Indeed we are using DSC template to provision tentacles to VM Scale Set machines programmatically. Next time this happens we collect the logs.
Do you have any upfront insights why DSC template re-application may cause thumbprint change? I would anticipate it to detect the tentacle already present and not try to change anything about it.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.