I have sucessfully discovered 3 servers with IP Addresses (10.45.232.10 - ovs1, 10.45.232.11 - ovs2, 10.45.232.12 - ovs3), created repositories, created and run virtual machines without any issues. However when I try to discover a fourth server 10.45.232.13 - ovs4, the job that is launched says that is is using IP address 10.45.232.11 which is the address of ovs2.
The job completes sucessfully but instead of discovering a fourth server (ovs4), it just moves the second server (ovs2) to the unassigned servers folder. However when you examine ovs2 the IP address has changed to that of the fourth server that I tried to discover. The console on ovs4 now says that it is managed.
So the VM Manager gets confused over the identity of the server it has just discovered, mixing up parts of two different servers.
I'm running VM Manager 3.1.1 on Oracle Enterprise Linux 5.5 and VM Server 3.1.1. The manager is a production install on 11g database.
Anyone seen this issue before or could suggest a workaround.
I'd say its something simple.... Like you've setup multiple network definitions and you have a overlap somewhere that has ovs2 in multiple definitions with different IP addresses. I don't know how this could happen but I imagine it is possible. Do you have any bonds setup besides bond0?