Dynatrace will Block a VM if Dynatrace is removed before the drain-script about bosh-oneagent-release HOT 9 CLOSED

Hi Christoph,

i copied this over to our internal issue tracker and we'll take measures to make the behaviour more stable here.
Most likely incorporating a variant of your suggested fix :-)

from bosh-oneagent-release.

Proposed changes added in PR #53
Once this is merged we'll create a new release :-)

from bosh-oneagent-release.

@Espe0n
After some internal discussions about this whole topic, one question came up:
Was our OneAgent uninstalled manually by someone or was this some kind of weird mishap during removal of our bosh-release?

from bosh-oneagent-release.

@Espe0n ping :-)

If i don't get a response, we'll assume the observed behaviour was caused by a manual intervention and close this as "won't do" for now.

from bosh-oneagent-release.

Hi @arthfl,
please excuse the late answer, I was not at the PC for a long time because of the holidays and am now working through the emails ...

Was our OneAgent uninstalled manually by someone or was this some kind of weird mishap during removal of our bosh-release?

The Dynatrace OneAgent was not manually removed. The Issue happend during an Update of the VM using Bosh. In the Log-Files we could see, that the Drain-Script was called and successfully removed the Dynatrace OneAgent.
However, for some reason Bosh didn't recognized this, so that the pre-start script was not called afterwards.
In the Result, the VM got stuck with the descripted Status.

Best Regard
Christoph

from bosh-oneagent-release.

Hi @Espe0n,

thanks for the answer :-)
Was this on a Linux or a Windows host?

from bosh-oneagent-release.

Hi,
the affected host is a Linux
Ubuntu 16.04

Best regards
Christoph

from bosh-oneagent-release.

Ok, got you.

Added some mitigations to the Linux job, will be merged with PR #53

from bosh-oneagent-release.

Released v1.3.1, which fixes this: https://github.com/Dynatrace/bosh-oneagent-release/releases/tag/v1.3.1

from bosh-oneagent-release.