Bug 448980 - ONBOOT=yes does not work with Bridge with no ports
Summary: ONBOOT=yes does not work with Bridge with no ports
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-29 19:07 UTC by Anthony Liguori
Modified: 2014-03-17 03:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-23 16:27:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Anthony Liguori 2008-05-29 19:07:35 UTC
Description of problem:

There is a check in /etc/init.d/network to that skips ifcfg- scripts if they are
of TYPE=Bridge.  Presumably, this is because bridges are brought up
automatically if an interface that is bridged by that bridge is brought up.

It is perfectly reasonable to define a bridge with no interfaces bridged.  For
instance, this is common when using virtualization when creating private
networks.  Right now, there doesn't seem to be a way to bring up a bridge with
no ports at boot time.

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

initscripts-8.76.2-1

How reproducible:


Steps to Reproduce:
1. Create a bridge in /etc/sysconfig/network-scripts/ifcfg-br0
2. Set ONBOOT=yes
3. Do not bridge any physical interfaces to br0
  
Actual results:

After booting, ifconfig br0 fails because br0 has not been brought up.

Expected results:

After booting, br0 should have been brought up.

Additional info:

Comment 1 iarly selbir 2009-03-22 19:15:15 UTC
is this problem happening yet?

Thanks for any reply.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Bill Nottingham 2009-03-23 16:27:31 UTC
I've tested this on Fedora 10 - it works there.


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