Oracle VM 3.0.3 is simply unusable after change of motherboard in OVMS

Question

Hi all,
so let's share some of my feelings about this crap. After so many issues during implementation this platform was finally set up. And was running for only one week with small number of errors. Then during friday motherboard in one of two Oracle VM servers in clustered pool failed and HP replaced it. Fine. Server runs, but Oracle VM manager is remembering old MAC addresses (!!!!!!!!!!!!!!!!!!!!!!!) and I'm not able to get rid off it. Maintenance mode doesn't help, removing from pool doesn't help, can't rediscover because of repository (which is not presented to this server), restart of ovmm doesn't help, restart of that node doesn't help, can't change MAC in web interface and can't remove that server from pool.
So what can I do? If I unpresent second node from storage repository, remove it from pool, destroy pool and create pool again will be there those virtual machines on SAN disk as before of they will be deleted as well? Which "clever" person decided to go through web interface only? How can I remove server from cluster via CLI? And why it remembers old MAC addresses??????????
I'm trying not be ugly, but this is not enterprise ready project. It's parody. Most of the garage-origin project are much more enterprise ready then this one :-(

Answer 1

Hi!
I'm working with the same case, I'll try to explain this once more + additional steps we tried.
We had fully functional cluster with 2 nodes, Node1 and Node2. Node1 overheated, shut down, all VM's migrated to Node2 and are working.MB was replaced by technical personnel. When server was brought up again, we see that new MAC addresses are in place in config files.
We can ssh to that box, no issue at all, network IS working properly.
On other server we have installed Oracle VM Manager. That "smart" manager can not get that Node1 has now different MAC, because that was the only thing which changed. We tried to rediscover the server for Node1, it complains that IP has changed and we need to delete Node1 from cluster and then rediscover the server (Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.IllegalOperationException: If the IP address of this server has changed, please delete the server: Node1, and re-discover.). Fine, we go do that, but now it complains that we can not do that because " OVMRU_002041E Cannot delete/remove pool file system: Pool filesystem for POOLNAME. Server pool: POOLNAME, still has servers in it". What the hell is that? It asks to remove whole pool filesystem just to remove the server which we need to add back again.
I tried to fixup the environment by this method (sh ./ovm_upgrade.sh dbuser=ovs dbpass=<password> --fixup) which did not work.
Then we tried to mess with MAC addresses in config files, we tried to set them to the OLD ones, which worked, our attempt was unsuccessful.
The question how to resolve this? To me this seems to be basic functionality, server burned down we need to replace it, we add it back and works. In Oracle VM solution this is not working, sad.
regards
Mjasnik
Edited by: user12122836 on May 22, 2012 7:19 AM
Edited by: user12122836 on May 22, 2012 7:20 AM
Edited by: user12122836 on May 22, 2012 7:20 AM
Edited by: user12122836 on May 22, 2012 7:39 AM