[Pkg-opennebula-devel] Bug#675930: Bug#675930: opennebula: Fails upgrade if suspended VMs are still there

Damien Raude-Morvan drazzib at drazzib.com
Mon Jun 4 09:50:27 UTC 2012

Hi Olivier,

Le 04/06/2012 11:14, Olivier Berger a écrit :
> I've had 2 VMs running on the node of my cloud, running testing (3.2).
> Upon upgrade to 3.4, I've had to update the DB schema.
> What am I supposed to do ?
> Does this mean that one should destroy all VMs before upgrading ? ... but how's one supposed to know :-/
> Shouldn't there be a check at preinst time to warn the admin at least ?

I would expect that users would read upstream upgrade guide before 
upgrading :

   Before installing OpenNebula 3.4, make sure you don't have
   any active VMs. Shutdown or delete all VMs.

Ii will be difficult on the long run to keep maintaining all tricks to 
keep package in sync with upstream handling...

More information about the Pkg-opennebula-devel mailing list