Bug 1071398 - Removing a bridged network over a bond (that is not to be removed) leaves the network bridge up.
Summary: Removing a bridged network over a bond (that is not to be removed) leaves the...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.4.1
Assignee: Antoni Segura Puimedon
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks: 1082275
TreeView+ depends on / blocked
 
Reported: 2014-02-28 16:35 UTC by Antoni Segura Puimedon
Modified: 2014-06-09 12:03 UTC (History)
9 users (show)

Fixed In Version: av2
Clone Of:
Environment:
Last Closed: 2014-05-08 13:38:29 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25203 0 None MERGED ifcfg: stop leaving leftover bridges when removing bonded networks Never
oVirt gerrit 26224 0 None MERGED ifcfg: stop leaving leftover bridges when removing bonded networks Never

Description Antoni Segura Puimedon 2014-02-28 16:35:18 UTC
Description of problem:
When having a network Foo that is defined as:
    {
     'name': 'foo',
     'bonding': 'bond0',
     'bridged': True,
    }
With the system having a preexisting bond:
    {
     'name': 'bond0',
    }

If you then want to remove the 'foo' network without touching the bond, the
bridge that was serving the 'foo' network will not be removed.

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


How reproducible: 100%


Steps to Reproduce:
1. vdsClient -s 0 addNetwork bridge=foo nics=eth2,eth3 bonding=bond0 bridged=true
2. vdsClient -s 0 setupNetworks networks='{foo:{remove:True}}'
3. brctl show

Actual results:
        bridge name    bridge id            STP enabled    interfaces
        ;vdsmdummy;    8000.000000000000    no
        foo            8000.001018e16d2c    no             bond0
        ovirtmgmt      8000.d067e5f075b4    no             em1


Expected results:
        bridge name    bridge id            STP enabled    interfaces
        ;vdsmdummy;    8000.000000000000    no
        ovirtmgmt      8000.d067e5f075b4    no             em1


Additional info:
This most probably also happens in 3.3

Comment 1 Itamar Heim 2014-03-02 05:42:52 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Martin Pavlik 2014-03-10 14:07:01 UTC
still reproducible in av2.1

[root@dell-r210ii-05 ~]# vdsClient -s 0 addNetwork bridge=foo nics=p1p1,p1p2 bonding=bond0 bridged=true
Done

[root@dell-r210ii-05 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
;vdsmdummy;		8000.000000000000	no		
foo		8000.90e2ba042d74	no		bond0
rhevm		8000.d067e5f07f02	no		em1

[root@dell-r210ii-05 ~]# vdsClient -s 0 setupNetworks networks='{foo:{remove:True}}'
Done

[root@dell-r210ii-05 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
;vdsmdummy;		8000.000000000000	no		
foo		8000.90e2ba042d74	no		bond0
rhevm		8000.d067e5f07f02	no		em1

Comment 3 Dan Kenigsberg 2014-03-22 16:00:39 UTC
Toni, please backport I3de692c7f089d6a9f404c3a2f6f568c12d8a985d to ovirt-3.4! (sorry for moving to ON_QA prematurely)

Comment 4 Sandro Bonazzola 2014-05-08 13:38:29 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.

Comment 5 Antoni Segura Puimedon 2014-06-09 12:03:01 UTC
It was already backported. Clearing the needinfo.


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