Bug 49606

Summary: Automatically reconnect VMs to bridge (4.2)
Product: UCS Reporter: Philipp Hahn <hahn>
Component: Virtualization - KVMAssignee: Philipp Hahn <hahn>
Status: CLOSED FIXED QA Contact: Erik Damrose <damrose>
Severity: normal    
Priority: P5 CC: damrose, heidelberger, oliver.bohlen, voelker
Version: UCS 4.2Flags: hahn: Patch_Available+
Target Milestone: UCS 4.2-5-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: Bug Report What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.429 Enterprise Customer affected?: Yes
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: 2019060521000629 Bug group (optional):
Max CVSS v3 score:
Bug Depends on: 47701, 49604    
Bug Blocks:    

Description Philipp Hahn univentionstaff 2019-06-06 15:28:25 CEST
+++ This bug was initially created as a clone of Bug #49604 +++
+++ This bug was initially created as a clone of Bug #47701 +++

If any UCRV interfaces/* changes, the network is re-configured and restarted.
With Qemu/KVM this removes and re-adds the bridge.
All VMs will loose their network connection until /usr/lib/univention-virtual-machine-manager-node-kvm/ucs-kvm-reconnect-bridge is manually invoked.

UCS should do this automatically:
 ucr set interfaces/br0/options/65535='post-up /usr/lib/univention-virtual-machine-manager-node-kvm/ucs-kvm-reconnect-bridge -b $IFACE'
Comment 1 Philipp Hahn univentionstaff 2019-06-06 15:48:40 CEST
[4.2-5] 5b2dd3fe71 Bug #47706 uvmm: Re-connect VMs to bridges on network restart
 .../debian/changelog                               |  6 +++
 .../debian/control                                 |  1 +
 ...ivention-virtual-machine-manager-node-kvm.if-up | 55 ++++++++++++++++++++++
 3 files changed, 62 insertions(+)

Package: univention-virtual-machine-manager-node
Version: 5.0.0-9A~4.2.0.201906061532
Branch: ucs_4.2-0
Scope: errata4.2-5

QA:
1. ifdown -a ; sleep 1 ; ifup -a ; brctl show
2. ucr commit ; brctl show
3. reboot ; brctl show

Released to _customer_ scope as errata4.2-5 is OoM - no YAML:

repo-copy-dsc -vvvv ../ucs_4.2-0-errata4.2-5/source/univention-virtual-machine-manager-node_5.0.0-9A~4.2.0.201906061532.dsc
repo-apt-ftparchive --release ${PWD##*/}
announce_ucs_customer_scope -c 00026 -r 4.2-0 -t -s $CUSTOMER
announce_ucs_customer_scope -c 00026 -r 4.2-0    -s $CUSTOMER

TODO after QA: ssh -t omar update_customer_mirror.sh 00026
Comment 2 Erik Damrose univentionstaff 2019-06-07 10:10:37 CEST
OK: /etc/network/if-up.d/univention-virtual-machine-manager-node-kvm
OK: use existing reconnect-kvm-bridge script
OK: executed per interface, if it is a bridge
OK: only run and try to connect when libvirt is running (interfaces are queried from libvirt)
OK: reconnect works for different scenarios,
 * ucr set interface/<name>/<something>
 * u-base-files package update
 * ifdown + ifup
OK: Network on restarted VMs after hypervisor reboot

Update only in customer scope, no yaml

Verified
Comment 3 Philipp Hahn univentionstaff 2019-06-07 12:51:21 CEST
DONE: update_customer_mirror.sh 00026
QA: apt install univention-virtual-machine-manager-node-kvm