Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1303165

Summary: bridge doesn't have mac address and is not on after creation
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: mclasen, tpelka
Target Milestone: rcKeywords: EasyFix
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1303665 (view as bug list) Environment:
Last Closed: 2016-04-29 12:29:31 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:    
Bug Blocks: 1303665    
Attachments:
Description Flags
screenshot none

Description Vladimir Benes 2016-01-29 18:17:30 UTC
Description of problem:
create bridge with default values after few attempts there is a bridge that has no mac and no state, going out and back to network tab fixes the issue

seems this is related:
Jan 29 19:14:40 trautenberg gnome-control-center.desktop[29793]: ** (nm-connection-editor:30380): WARNING **: Unsupported connection type 'generic'

see attached picture

[vbenes@trautenberg ~]$ nmcli device show bridge0
GENERAL.DEVICE:                         bridge0
GENERAL.TYPE:                           bridge
GENERAL.HWADDR:                         46:D3:D8:51:C8:39
GENERAL.MTU:                            1500
GENERAL.STATE:                          70 (connecting (getting IP configuration))
GENERAL.CONNECTION:                     Bridge connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/44


Version-Release number of selected component (if applicable):
control-center-3.14.5-8.el7.x86_64
NetworkManager-1.0.6-27.el7.x86_64


How reproducible:


Steps to Reproduce:
1.create several bridges in c-c network

Actual results:
after a while there is invalid bridge state 

Expected results:
correct state

Additional info:

Comment 1 Vladimir Benes 2016-01-29 18:18:35 UTC
Created attachment 1119494 [details]
screenshot

Comment 3 Tomas Pelka 2016-02-09 20:24:22 UTC
no more fast

Comment 4 Bastien Nocera 2016-04-29 12:29:31 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.