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 1075195

Summary: provide bridge support
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Pirko <jpirko>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dcbw, gscrivan, jstodola, mkovarik, rkhan, steved
Target Milestone: rcFlags: mleitner: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-19.31.96-1 Doc Type: Bug Fix
Doc Text:
Cause: Anaconda did not support creating network bridges. Consequence: No network bridge. Fix: Write code. Result: Anaconda now supports the creation of network bridges with the Network Spoke in the GUI or via the kickstart network command like so: network --device=br0 --bridgeslaves=eth1,eth2 --bridgeopts=stp=no
Story Points: ---
Clone Of:
: 1146509 1172527 (view as bug list) Environment:
Last Closed: 2015-03-05 13:59:29 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: 1146509    
Bug Blocks: 1112660, 1172527    
Attachments:
Description Flags
NM log: activating bridge connection fails.
none
ifcfg.log
none
NM log: activating bridge connection fails. (using nm-c-e) none

Description Jiri Pirko 2014-03-11 16:53:30 UTC
Bridge is currently not supported by Anaconda. It is supported in NM and it should be fairly easy to add the support to Anaconda. Please do so.

Comment 1 Radek Vykydal 2014-09-03 09:02:12 UTC
Created attachment 933986 [details]
NM log: activating bridge connection fails.

07:41:31,201 INFO NetworkManager: <debug> [1409730091.201873] [platform/nm-linux-platform.c:1785] link_add(): link: add link 'br0' of type 'bridge' (196608)
07:41:31,219 ERR NetworkManager: <error> [1409730091.219958] [platform/nm-linux-platform.c:1366] add_object(): Netlink error adding 0: br0 <DOWN> mtu 0 bridge: Operation not supported
07:41:31,220 WARNING NetworkManager: <warn> (br0): failed to create bridge master interface for 'bridge-br0': unknown error

Comment 2 Radek Vykydal 2014-09-03 09:07:29 UTC
Dan, I am not able to bring bridge connection in installer environment (see comment #1). I tried to create the connections using nm-c-e (the above log) and nmcli. Am I doing something wrong, or is installer environment missing something?
I am using rhel 7.0 GA.

I will attach also ifcfg.log.

Comment 3 Radek Vykydal 2014-09-03 09:19:35 UTC
Created attachment 933993 [details]
ifcfg.log

Comment 4 Radek Vykydal 2014-09-03 10:23:16 UTC
Created attachment 934036 [details]
NM log: activating bridge connection fails. (using nm-c-e)

(In reply to Radek Vykydal from comment #2)
> Dan, I am not able to bring bridge connection in installer environment (see
> comment #1). I tried to create the connections using nm-c-e (the above log)

Correction: the log in comment #1 is from using nmcli in installer, this log is from using nm-c-e in installer.

Comment 6 Radek Vykydal 2014-10-01 06:26:16 UTC
*** Bug 1148004 has been marked as a duplicate of this bug. ***

Comment 7 Giuseppe Scrivano 2014-10-01 12:31:00 UTC
Another user experienced a similar problem:

just tried to install from RHEL-7.1-20140930.n.0-Workstation-x86_64-boot.iso

cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=RHEL-7.1\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
hashmarkername: anaconda
kernel:         3.10.0-171.el7.x86_64
package:        anaconda-19.31.95-1
product:        Red Hat Enterprise Linux
reason:         AttributeError: 'RHEL7_NetworkData' object has no attribute 'bridgeslaves'
release:        Red Hat Enterprise Linux Client release 7.1 Beta (Maipo)
release_type:   pre-release
version:        7.1

Comment 10 errata-xmlrpc 2015-03-05 13:59:29 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.

https://rhn.redhat.com/errata/RHBA-2015-0312.html