Upgrade from RHEVM 3.0 to RHEVM 3.1 gone wrong

Hi All,

I have have been trying to resolve an issue that has happened to me, and although I have a case opened it might be worth opening it up for discussion and perhaps see if the collective effort can help to resolve the issue quickly.

I have a Physical server running RHEL 6.2 and within RHEVM 3.0, I had a cluster of 1 host with an FC storage and 1 Cluster of 1 host running VMs in local storage with everything working fine. Everything began when I attempted an upgrade to 3.1, seemed easy enough but the upgrade failed and the roll back plan did not work. Thankfully the upgrade process did a database backup for me and I was left with an sql file and little else. After much research and opening a case, I ended up installing a fresh install of server and RHEVM 3.0 software, I now had a working server but no clusters/hosts/vms from before.

The sql file had engine as the database not "rhevm", i am told rhevm was the 3.0 version of the database and "engine" the 3.1 version. I opted to rename the intances of the word "engine" to "rhevm". I went into the postgress database environment and renamed the original "blank" rhevm db to something else and injected the sql file. It created the database just fine, but the GUI no longer worked. I released that the database created did not have any permissions as the blank rhevm database. Created these to be the same and then GUI worked fine. I was now able to see the old clusters/hosts/vms/networks, etc but all were in an unknown state.  I followed a guide i found in the knowledgebase called "How to restore rhevm from a database backup after a crash" which gave me some info on how to proceed. I had to put the SPM status to "null" via some sql commands in the guide. I now needed to put the hosts in maintenance mode and activate. But it saw that VMs were running so it could not go to maintenance mode. I managed to reboot the host with the FC storage and worked fine, the host was seen and put into maintenance and then had to remove and re-register the host, only then was the host seen in active mode. I saw all vms and did not lose any data.

Now my focus went to the other host, the one with locally stored VMs (one VM being a server in production). I am worried that if  do the same as for my other host, when i re-register the host it will erase all my locally stored VMs, thus removing the production server!.

I would welcome any sugguestions on this matter, i am sure this must have happened befoe to someone.

Thank you

Brandon Saccone