This content has been marked as final. Show 7 replies
You're right, I didn't. Apologies.
It's VM Manager 184.108.40.2066. The fact that you mention that 3.2.2 fixes this bug amuses me greatly as I've just recovered from having to reinstall VM Manager after my 3.1.1->3.2.1 VM Manager update failed spectacularly. Attempting another update from 3.2.1->3.2.2 fills me with dread. Even though I dumped the OracleDB database for the OVS repository and went for the new, local, MySQL DB instead I'm worried I'm going to have to go through a clean install again.
But a fix for this bug, you say? In 3.2.2, you say? Nothing I can do in 3.2.1 about it?
Also, I note from the readme for the 3.2.2 update that the fix is:
16287721 Fixes the "Object Not Found" issue when a virtual disk file has been manually removed (or renamed)
This is a physical disk...
Edited by: Ben A on 08-Mar-2013 05:43
I agree with you 100 percent. I don't why on the world they keep revising distributions and requiring manual upgrades to get certain "bug" fixes. I hope they change this soon. Just seems so silly to me. I've been stable on 3.1.1 for months. I hate to even think of actually upgrading given this. I was lucky in that I stated testing with 3.0.1 and 3.1.1 came out during my testing. I would have hated to try to upgrade from 3.0.1 to 3.1.1 in a production environment.
I just ran a clean upgrade of the VM manager from 3.2.1 to 3.2.2 build 520 using MySQL. It went smooth. I do believe the "readme" details a bug fix associated with upgrading from 3.1.1 to 3.2.1.
Do a rescan physical disks from your VM server itself. Some people have had problems with servers rebooting doing this when there is I/O taking place on the server. Might want live migrate your guests before doing this. Rebooting should have cleared it once the Server synced with the VM Manager but the rescan from the VM Manager might get the server and the manager in sync.
Good to know the upgrade from 3.2.1 to 3.2.2 went smoothly. That gives me some confidence. I'll try it on Monday. 3.1.1 to 3.2.1 appeared to work, but it futzed something badly. I hope I never have to go through that again.
How do I do a rescan of the physical disks from the VM Server itself? I didn't think there was any way to do that except through the VM Manager GUI. As for live migration, I can't do that as there's no clustering and no shared filesystems/disks/etc. Everything is local. However, the guests aren't live yet, so I can shut them down whenever I like. Rebooting the VM Server doesn't seem to have cleared things, neither has rescans initiated by the VM Manager. So... How do I do this rescan on the VM Server?
Thanks for that. At the end all it said was:
0 new device(s) found.
0 device(s) removed.
So I doubt that was going to be the solution. The functionally seems completely broken as the new (replacement, existing) RAID volume isn't deletable either. Any other thoughts, please?
Very much appreciating the help.
I have now done an apparently flawless (a first for Oracle VM software) upgrade of Oracle VM Manager (and the Servers, too) from 3.2.1 to 3.2.2-520.
Unfortunately I still cannot delete old physical disk references from VM Servers via the VM Manager GUI. They're marked as "Warning" (in red), and also 'StorageDeviceOfflineEvent' "Physical disk is offline", but the option to delete the thing itself is greyed out.
Does anyone have any suggestions, please?