29 Nov 2023 09:03 PM
Hi,
We're experiencing an issue with updating VM tools if Dynatrace is installed on the system:
If the installation occurs while the service is running:
The problem does not occur if the Dynatrace service is stopped during the installation:
We have Dynatrace agent version 1.269.180 installed, and we were installing VM Tools version 12.3.5.22544099.
Radek
Solved! Go to Solution.
30 Nov 2023 07:24 AM
Sounds reasonable to open a support ticket. Is this Windows or Linux? I would recommend updating the OneAgent anyway. Also check the oneagentnetwork logs as this is the only component which touches network interfaces directly.
30 Nov 2023 07:46 AM
I will set up a ticket in support and we will do an OA update with the client today. I'll let you know when I find out what was the cause.
Radek
30 Nov 2023 07:50 AM
I remember there were possible issues with the temporary loss of connectivity with Windows and OneAgent due to the packet capture library and some missing windows updates a while ago. However, definitely a support ticket needs to be raised.
02 Feb 2024 10:11 AM
Hi,
We stumbled across this issue as well, did you receive any feedback @radek_jasinski ?
02 Feb 2024 11:00 AM
Hi @jonhaugen
Support recommended upgrading OneAgent to the latest version (in our case it was 1.282 and the problem was completely solved). Do you have any agent log entries?
Radek
02 Feb 2024 11:11 AM - edited 02 Feb 2024 11:14 AM
Thanks for your reply!
I don't have any logs from the previous patch windows unfortunately, but we are prepared to take snapshots on VM's where the upgrade might fail.
We run Dynatrace Managed and just upgraded to 1282 today. Do you have any details from support for why upgrading might help?
Edit: Looking in to the release notes, no issues regarding vmware tools was mentioned.
02 Feb 2024 12:43 PM
They asked me for an update during the diagnosis.
When the problem stopped I didn't go into why, as I assumed a bug in the agent version.
01 Mar 2024 03:07 PM
The issue is related to a known bug in the Npcap driver delivered with OA.
Currently, we're working to release OA, which will provide a fix to that problem.
Stopping and starting OA during the VMware tools update is still a valid workaround.