Description Erik Damrose 2014-11-12 11:19:40 CET

At the start of the update to UCS 4 running KVM instances are suspended by libvirt-bin as it gets removed. libvirt-daemon-system is installed, but fails to bring up the suspended guests, which in turn causes univention-virtual-machine-manager-node-kvm remain unconfigured. Thus, the updater reports a failed update to UCS 4.

Solution: Check for running instances in the UCS 4 preup script and deny updating until they are shutoff.

Probably all instances that were suspended on 3.2 are affected.

Powering off all VMs and starting them after the upgrade works fine.


Excerpt from updater.log:

Entfernen von libvirt-bin ...
Running guests on qemu:///system URI: ucs40-64-test
Suspending guests on qemu:///system URI...
Suspending ucs40-64-test: Suspending ucs40-64-test: done 

[...]

libvirt-daemon-system (1.2.7-11.129.201410301533) wird eingerichtet ...
[...] Starting libvirt management daemon: libvirt ok

Resuming guests on qemu:///system URI...
Resuming guest ucs40-64-test: 
error: Failed to start domain ucs40-64-test
error: internal error: early end of file from monitor: possible problem:
qemu: warning: error while loading state for instance 0x0 of device 'ram'
load of migration failed

invoke-rc.d: initscript libvirt-guests, action "start" failed.
dpkg: Fehler beim Bearbeiten von libvirt-daemon-system (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[...]

dpkg: Abhängigkeitsprobleme verhindern Konfiguration von univention-virtual-machine-manager-node-kvm:
 univention-virtual-machine-manager-node-kvm hängt ab von libvirt-daemon-system; aber:
  Paket libvirt-daemon-system ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten von univention-virtual-machine-manager-node-kvm (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert