Bug 1082275 - [MultiHost] Bridge still exists for the network when updating that network to be non-VM (net over bond)
Summary: [MultiHost] Bridge still exists for the network when updating that network to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.4.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.4.0
Assignee: lpeer
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On: 1071398
Blocks: rhev3.4rc
TreeView+ depends on / blocked
 
Reported: 2014-03-30 08:22 UTC by GenadiC
Modified: 2016-02-10 19:55 UTC (History)
9 users (show)

Fixed In Version: av8
Doc Type: Bug Fix
Doc Text:
With this update, the presence of network bridges on logical networks is now correctly updated when bonded logical networks are removed.
Clone Of:
Environment:
Last Closed: 2014-06-09 13:29:57 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdsm log with sw1 as problematic network (1.40 MB, text/x-log)
2014-03-30 08:22 UTC, GenadiC
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0504 0 normal SHIPPED_LIVE vdsm 3.4.0 bug fix and enhancement update 2014-06-09 17:21:35 UTC
oVirt gerrit 26224 0 None None None Never

Description GenadiC 2014-03-30 08:22:46 UTC
Created attachment 880265 [details]
vdsm log with sw1 as problematic network

Description of problem:
If you create VM network and attach it to Host over bond, then updating that network to be non-VM will not remove the bridge for that network

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create VM network and attach it to the bond on the Host
2. Update network to be non-VM
3. Check if the bridge exists on the host for that network (brctl show)

Actual results:
Bridge exists 

Expected results:
non-VM network is supposed to be non-VM (without a bridge)

Additional info:
getVdsCaps shows correct configuration for sw1 that is supposed to be non-VM, but brctl show shows it as VM:

bridge name     bridge id               STP enabled     interfaces
;vdsmdummy;             8000.000000000000       no
rhevm           8000.001d0968714e       no              eth0
sw1             8000.001517a76a4c       no              bond0


networks = {'rhevm': {'addr': '10.35.128.10',
                              'bridged': True,
                              'cfg': {'BOOTPROTO': 'dhcp',
                                      'DEFROUTE': 'yes',
                                      'DELAY': '0',
                                      'DEVICE': 'rhevm',
                                      'NM_CONTROLLED': 'no',
                                      'ONBOOT': 'yes',
                                      'STP': 'no',
                                      'TYPE': 'Bridge'},
                              'gateway': '10.35.128.254',
                              'iface': 'rhevm',
                              'ipv6addrs': ['fe80::21d:9ff:fe68:714e/64'],
                              'ipv6gateway': '::',
                              'mtu': '1500',
                              'netmask': '255.255.255.0',
                              'ports': ['eth0'],
                              'stp': 'off'},
                    'sw1': {'addr': '',
                            'bridged': False,
                            'gateway': '',
                            'iface': 'bond0',
                            'interface': 'bond0',
                            'ipv6addrs': ['fe80::215:17ff:fea7:6a4c/64'],
                            'ipv6gateway': '::',
                            'mtu': '1500',
                            'netmask': ''}}

Comment 1 Dan Kenigsberg 2014-03-30 21:00:07 UTC
Effectively, this bug is the rhev clone of ovirt's bug 1071398.

Comment 2 GenadiC 2014-04-30 11:28:54 UTC
Verified in AV7

Comment 3 errata-xmlrpc 2014-06-09 13:29:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0504.html


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