Hi, hoping someone can help or point me in the right direction.
I have an issue with OctopusDSC when running from Azure Automation, specifically the cTentacleAgent resource.
For context, we have a VM hosting Octopus sitting behind an Application Gateway and we also power down this VM during our off hours for cost saving.
This leads me to our issue. Whenever the server is shut down, a 502 is thrown from the Application Gateway. This then causes cTentacleAgent on other servers to throw a “non-terminating” error and causes the whole DSC compliance check to fail. See pictures 1 & 2
My question is, is there a way around this behaviour from the cTentacleAgent resource? It’s not really a problem as far as cTentacleAgent goes, however it causes me to not be able to see the compliance of any other resources I have running against the node.
Preferred behaviour would be to have the resource mark the node as non-compliant.