I have noticed 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. This is not ideal as I am unable to have compliance reporting during the period that the server is off as the whole configuration fails for any nodes I have this set up with, not just the cTentacleAgent configuration.
Preferred behaviour would be to have the resource mark the node as non-compliant.
I have already raised this issue in Slack (recieved no response from anyone) and created a topic in help.octopus.com "cTentacleAgent Server Url" and was told my options were:
Fix the issue myself in the OctopusDSC module - Not feasible as I import the module into Azure Automation from the PS Gallery
Turn on the server 24/7 to avoid the issue - Defeats the purpose of trying to save money by turning it off in the first place
Raise the issue on this repo in the hopes it doesn't get deprioritised into oblivion
Hi,
I have noticed 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. This is not ideal as I am unable to have compliance reporting during the period that the server is off as the whole configuration fails for any nodes I have this set up with, not just the cTentacleAgent configuration.
Preferred behaviour would be to have the resource mark the node as non-compliant.
I have already raised this issue in Slack (recieved no response from anyone) and created a topic in help.octopus.com "cTentacleAgent Server Url" and was told my options were:
Screenshots of issue:
My DSC code: