Bug 1303665

Summary: bridge cannot be downed after upping it manually
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: control-centerAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: bnocera, desktop-qa-list, mclasen
Target Milestone: rcKeywords: EasyFix
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1303165 Environment:
Last Closed: 2016-04-29 12:25:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1303165    
Bug Blocks:    

Comment 1 Vladimir Benes 2016-02-01 15:45:02 UTC
not sure if this is the same bug but this scenario is broken as well:

1. create new not-automatic bridge with manually set IP to 192.168.1.15/24
2. turn it on via toggle button
 it should be visible via ip a s command
3. turn it off via toggle button
 it shouldn't be visible via ip a s command but it still is

not sure if it isn't a dupe of bug 1303165 as going out and back into network fixes the behavior.

Comment 2 Vladimir Benes 2016-02-05 10:38:13 UTC
aha, when you go from Network and back it looks like working well. So just this bug is more a test case holder.

Comment 3 Bastien Nocera 2016-04-29 12:25:35 UTC
Support for enterprise networking features will be removed in future versions of GNOME and of RHEL 7.x. We advise that you test Cockpit instead, which is better suited to manipulate enterprise networking feature.

Teaming support for Cockpit is tracked at:
https://github.com/cockpit-project/cockpit/issues/4330

Bonding, bridging and VLAN support are already implemented.