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

Olivier Berger olivier.berger at it-sudparis.eu
Mon Jun 4 14:52:52 UTC 2012


Damien Raude-Morvan <drazzib at drazzib.com> writes:

> 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 :
> http://opennebula.org/documentation:rel3.4:upgrade

I'm afraid this isn't a valid expectation for a Debian

At least, there should be a NEWS big red warning IMHO.

>    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...

That's the fate of the Debian maintainer : never pretended it would be

Anyway, for the problem at stake, I guess there could be some kind of a
check in a script that uses onevm list to check the status for instance
(or some lower level API I'm not aware of).

Thanks in advance.

Best regards,

Olivier BERGER 
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

More information about the Pkg-opennebula-devel mailing list