Bug 715060 - VM Bridges are in the "down" state on reboot
Summary: VM Bridges are in the "down" state on reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: initscripts
Version: 5.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 18:27 UTC by John Brier
Modified: 2018-11-14 14:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-19 22:27:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 8 Bill Nottingham 2011-07-19 18:54:55 UTC
This is fixed incidentally with the fix for bug 664091, should be in 5.7.

Comment 9 John Brier 2011-07-19 19:27:44 UTC
Thanks, I was looking at the patch mentioned in that BZ (https://bugzilla.redhat.com/attachment.cgi?id=469405&action=diff) and it looks like it's already assuming ifcfg-lo$ is in place.. is there another patch which will bring that in to RHEL 5.7?

diff --git a/rc.d/init.d/network b/rc.d/init.d/network
index 482bb7b..b31060b 100755
--- a/rc.d/init.d/network
+++ b/rc.d/init.d/network
@@ -46,7 +46,7 @@ cd /etc/sysconfig/network-scripts
 interfaces=$(ls ifcfg* | \
            LANG=C sed -e "$__sed_discard_ignored_files" \
                       -e '/\(ifcfg-lo$\|:\|ifcfg-.*-range\)/d' \
-                      -e '/ifcfg-[A-Za-z0-9\._-]\+$/ { s/^ifcfg-//g;s/[0-9]/
&/}' | \
+                      -e '/ifcfg-[A-Za-z0-9#\._-]\+$/ { s/^ifcfg-//g;s/[0-9]/
&/}' | \
            LANG=C sort -k 1,1 -k 2n | \
            LANG=C sed 's/ //')
 rc=0

Comment 10 Bill Nottingham 2011-07-19 19:34:31 UTC
Yes, that patch is a patch to the original patch.

Comment 11 John Brier 2011-07-27 15:48:56 UTC
I think this is fixed with

http://rhn.redhat.com/errata/RHSA-2011-1090.html

Comment 12 Chris Williams 2012-01-19 22:27:40 UTC
Closing based on comment 11.


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