Bug 49604 – Automatically reconnect VMs to bridge (4.3)

Bug 49604 - Automatically reconnect VMs to bridge (4.3)


Summary:	Automatically reconnect VMs to bridge (4.3)

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - KVM
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.3-4-errata
Assigned To:	Philipp Hahn
QA Contact:	Erik Damrose

URL:
Keywords:

Depends on:	47701
Blocks:	49606
	Show dependency tree / graph

Reported:	2019-06-06 14:43 CEST by Philipp Hahn
Modified:	2019-06-07 13:31 CEST (History)
CC List:	4 users (show)

See Also:
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:

Flags:	hahn: Patch_Available+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2019-06-06 14:43:55 CEST

+++ 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

2019-06-06 15:27:41 CEST

[4.3-4] 22152c4436 Bug #47701 uvmm: Re-connect VMs to bridges on network restart
 .../univention-virtual-machine-manager-node.yaml   | 10 ++++
 .../debian/changelog                               |  6 +++
 .../debian/control                                 |  1 +
 ...ivention-virtual-machine-manager-node-kvm.if-up | 55 ++++++++++++++++++++++
 4 files changed, 72 insertions(+)

Package: univention-virtual-machine-manager-node
Version: 6.0.0-5A~4.3.0.201906061447
Branch: ucs_4.3-0
Scope: errata4.3-4

[4.3-4] 95686b44b2 Bug #49604: univention-virtual-machine-manager-node 6.0.0-5A~4.3.0.201906061447
 doc/errata/staging/univention-virtual-machine-manager-node.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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

Comment 2 Erik Damrose

2019-06-07 10:08:51 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
OK: yaml
Verified

Comment 3 Erik Damrose

2019-06-07 13:31:06 CEST

<http://errata.software-univention.de/ucs/4.3/526.html>