I am testing AOA version 24.4.1.hf1 and hope to deploy it to production next week. A couple of days ago, the UC user has spawned a Windows agent it named TMP. The Windows agent software is 24.4.1+build.1750257831752. It is offline and has the IP Address of another Windows Agent's Replication IP (ending in 139). The logs for this new agent TMP are located on the original agent (ending in 15), whose Replication IP it assumed. I have attached the log file.
In our system, AOA is in AWS using Kubernetes and our agents are in "on-prem" in Openstack P9.
Has anyone had a similar experience or know why this may have happened?