Azure VM Extension changes tenant tags on reboot


We have used Azure VM with the Octopus Tentacle extension to automatically register tentacle for new vm. We configure tenant tags for the machine after the tentacle is registered. It worked very well until we stop and start the vm. The VM extension sometimes don’t get the heartbeat from the tentacle quickly enough, so it decides to re-register the tentacle. However, we found it silently used --force parameter on register-with command so it overwrites the tenant tags of the machine on Octopus server.

Is this intentional or can we have the --force optional or removed. I don’t really think people would normally change the configuration on tentacle and rely on the extension to resync it with the server. Sounds like the --force shouldn’t be needed?

We also found this comment on a similar issue which seems related to this bug.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.