Univention Bugzilla – Bug 33006
Prevent Univention-System-Setup network configuration while KVM/Xen is in use.
Last modified: 2013-12-10 10:31:35 CET
+++ This bug was initially created as a clone of Bug #30816 +++ +++ This bug was initially created as a clone of Bug #28389 +++ TODO: univention-virtual-machine-manager-node-kvm With uvmm-node-Xen/Kvm doing the ethX/pethX shuffle, this breaks the UMC logic: It detects the renamed physical interface 'pethX' and generates a profile for that instead of the 'ethX' wich "ifup" will see before the dance is done. Therefore the uvmm-node-* packages will set a new UCRV umc/modules/setup/network=false, which should disable the full UMC network page and show a link to <http://docs.univention.de/computers-3.2.html#uvmm> instead explaining the situation.
The UCRV umc/modules/setup/network=33006 is set in the uvmm-node-{kvm,xen}.postinst unless the scripts are already deactivated. The number 33006 represents this bug number and is used to distinguish this issue from future issues also requiring the page to be disabled. ChangeLog: Added support to configure Bridge, Bond and VLAN interfaces. This is blocked while the deprecated KVM and Xen script are still used, which normally setup a bnetwork ridge for virtualisation. See <ulink url="http://docs.univention.de/computers-3.2.html#uvmm"/> for detailed instructions (<ulink url="&ucsbug;30816">Bug 30816</ulink>, <ulink url="&ucsbug;30878">Bug 30878</ulink>, <ulink url="&ucsbug;33006">Bug 33006</ulink>). r45692 | Bug #33006: UVMM: Disable setup network univention-virtual-machine-manager-node_2.0.4-1.71.201310291707 <http://jenkins.knut.univention.de:8080/view/Doku/job/UCS-3.2-0%20Handbook%20Extended/lastSuccessfulBuild/artifact/webroot/computers-3.2.html#uvmm>
(In reply to Philipp Hahn from comment #1) > ChangeLog: ... > which normally setup a [-b-]network {+b+}ridge for virtualisation. r45693 | Bug #33006: UVMM: Disable setup network
(In reply to Philipp Hahn from comment #1) > The UCRV umc/modules/setup/network=33006 is set in the > uvmm-node-{kvm,xen}.postinst unless the scripts are already deactivated. > The number 33006 represents this bug number and is used to distinguish this > issue from future issues also requiring the page to be disabled. Please use a more describable key / value pair.
Created attachment 5543 [details] A not so earnest proposal ... To be future proof two develops came up with this clever idea and agreed to use the bug number, which can be used to provide additional information and is guaranteed to be unique. Sure we could prefix the "33006" with "issue-" or "https://forge.univention.org/bugzilla/show_bug.cgi?id=", but that wouldn't help IMHO. If you have a better idea for name and value, please say so, I'm open to suggestions. I'm too tired to come up with a good alternative and I'm unwilling to spend any more time on this minor issue how to name this flag variable and its value.
You want to disable the network config dialog because the virtualization packages use a not compatible network configuration. My suggestion: umc/modules/setup/network/disabled/by=xen umc/modules/setup/network/disabled/by=kvm umc/modules/setup/network/disabled/by=none New reasons can be easily added.
As discussed with Philipp, I've now renamed the variable as suggested. The variable will be removed in postrm.
I fixed xen.postrm to remove the variable if it is set to "xen" (instead of "kvm").
Network page hidden if xen/kvm is installed: OK UCRVs set during installation: OK UCRVs unset during deinstallation: FAIL, does not work for xen.
(In reply to Lukas Walter from comment #8) > UCRVs unset during deinstallation: FAIL, does not work for xen. Florian fixed it and I rebuild the package now. It works now.
(FAIL): Documentation not updated and still refers to UCRV umc/modules/setup/network -> OK (r45839): I fixed the variable name in extended-docs/computers-3.2.xml OK: umc/modules/setup/network/disabled/by is set and removed correctly by *-node-kvm and -xen packages OK: works with system setup VERIFIED
(In reply to Erik Damrose from comment #10) > (FAIL): Documentation not updated and still refers to UCRV > umc/modules/setup/network virtualization/univention-virtual-machine-manager-node/debian/univention-virtual-machine-manager-node-common.univention-config-registry-variables is now wrong too...
(In reply to Philipp Hahn from comment #11) > (In reply to Erik Damrose from comment #10) > > (FAIL): Documentation not updated and still refers to UCRV > > umc/modules/setup/network > > virtualization/univention-virtual-machine-manager-node/debian/univention- > virtual-machine-manager-node-common.univention-config-registry-variables is > now wrong too... I've opened Bug #33111 for it.
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".