[Pkg-opennebula-devel] Bug#675930: opennebula: Fails upgrade if suspended VMs are still there
Olivier Berger
olivier.berger at it-sudparis.eu
Mon Jun 4 09:14:49 UTC 2012
Package: opennebula
Version: 3.4.1-2
Severity: normal
Hi.
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.
But :
# su - oneadmin -c "onedb upgrade -v --sqlite /var/lib/one/one.db"
Version read:
3.2.1 : Database migrated from 2.0 to 3.2.1 (OpenNebula 3.2.1) by onedb command.
Sqlite database backup stored in /var/lib/one/one.db.bck
Use 'onedb restore' or copy the file back to restore the DB.
> Running migrator /usr/lib/one/ruby/onedb/3.2.1_to_3.3.0.rb
> Done
> Running migrator /usr/lib/one/ruby/onedb/3.3.0_to_3.3.80.rb
You can't have active VMs. Please shutdown or delete the following VMs:
ID STAT NAME
70 susp vm1
71 susp vm2
Error while upgrading from 3.2.1 to 3.3.80
The database will be restored
Sqlite database backup restored in /var/lib/one/one.db
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 ?
Many thanks in advance.
Best regards,
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (300, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages opennebula depends on:
ii apg 2.2.3.dfsg.1-2
ii genisoimage 9:1.1.11-2
ii libc6 2.13-32
ii libgcc1 1:4.7.0-8
ii libmysqlclient18 5.5.23+dfsg-2
ii libsqlite3-0 3.7.12.1-1
ii libssl1.0.0 1.0.1c-1
ii libstdc++6 4.7.0-8
ii libxml2 2.7.8.dfsg-9.1
ii libxmlrpc-c++4 1.16.33-3.1
ii libxmlrpc-core-c3 1.16.33-3.1
ii opennebula-tools 3.4.1-2
ii wget 1.13.4-3
Versions of packages opennebula recommends:
ii libjs-jquery 1.7.2+debian-1
ii libjs-jquery-ui 1.8.ooops.20+dfsg-1
Versions of packages opennebula suggests:
pn mysql-server <none>
pn ruby-amazon-ec2 <none>
pn ruby-uuidtools <none>
-- debconf-show failed
More information about the Pkg-opennebula-devel
mailing list