Univention Bugzilla – Bug 36476
Update from UCS 3.2 -> 4.0 breaks libvirtd config, no connection to node possible
Last modified: 2014-11-26 06:54:40 CET
The package libvirt-bin is replaced by libvirt-daemon-system in UCS 4 The libvirt-bin initscript in uvmm-node-common was renamed to libvirtd in r54669 When updating from 3.2, the link univention-virtual-machine-manager-node-common -> libvirt-bin does not get updated, which now points to the libvirt-bin packages initscript -> the link is not created on a new ucs4 kvm host, so on updating from 3.2 it should be removed After the update, we now have 2 init scripts that try to start libvirtd: # dpkg -S /etc/init.d/libvirtd lokale Umleitung von: /etc/init.d/libvirtd lokale Umleitung zu: /etc/init.d/libvirtd.debian libvirt-daemon-system: /etc/init.d/libvirtd # dpkg -S /etc/init.d/libvirt-bin libvirt-bin: /etc/init.d/libvirt-bin Only libvirt-bins config remains: # dpkg -l libvirt-bin rc libvirt-bin ->libvirtd and libvirt-bin both get started in the UCS default runlevel, libvirt-bin gets executed first due to its name, which loads the wrong config and breaks libvirtd: libvirtd does not listen on any port. When updating, libvirt-bin should at least be removed from all runlevels. I think it would be better, if all remaining libvirt-bin related configuration would be removed.
r55535 | Bug #36376 UVMM: Remove broken symlink (In reply to Erik Damrose from comment #0) > When updating from 3.2, the link > univention-virtual-machine-manager-node-common -> libvirt-bin > does not get updated, which now points to the libvirt-bin packages initscript > -> the link is not created on a new ucs4 kvm host, so on updating from 3.2 > it should be removed It's removed now. > After the update, we now have 2 init scripts that try to start libvirtd: ... > ->libvirtd and libvirt-bin both get started in the UCS default runlevel, > libvirt-bin gets executed first due to its name, which loads the wrong > config and breaks libvirtd: libvirtd does not listen on any port. The old libvirtd is stopped using the original Debian script before the UCS variant using runit is started. > When updating, libvirt-bin should at least be removed from all runlevels. I > think it would be better, if all remaining libvirt-bin related configuration > would be removed. The broken links are now removed as this is caused by UCR diverting files which "dpkg-maintscript-helper rm_conffile" tries to remove. Package: univention-virtual-machine-manager-node Version: 3.0.3-1.84.201411071940 Branch: ucs_4.0-0
Verified: Update + New installation works
I do not know why it worked in my previous test, but during the PT both initscripts remained active. I will change the line to forcibly remove the script with update-rc.d -f libvirt-bin remove
r55830 univention-virtual-machine-manager-node 3.0.3-2.85.201411141808
(In reply to Erik Damrose from comment #4) > r55830 univention-virtual-machine-manager-node 3.0.3-2.85.201411141808 OK: -f Force removal of symlinks even if /etc/init.d/name still exists. OK: r55830 OK: dpkg-deb -e univention-virtual-machine-manager-node-common_3.0.3-2.85.201411141808_all.deb tmp && grep update tmp/*
UCS 4.0-0 has been released: http://docs.univention.de/release-notes-4.0-0-en.html http://docs.univention.de/release-notes-4.0-0-de.html If this error occurs again, please use "Clone This Bug".