Bug 236524 – bonding patch breaks network

Bug 236524 - bonding patch breaks network

Summary:	bonding patch breaks network

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	xen (Show other bugs)
Sub Component:
Version:	6
Hardware:	All Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Herbert Xu
QA Contact:	Martin Jenner
Docs Contact:

URL:	http://www.redhat.com/archives/fedora...
Whiteboard:
Keywords:

Depends On:	237667
Blocks:
	Show dependency tree / graph

Reported:	2007-04-15 21:15 EDT by Curtis Doty
Modified:	2008-02-26 19:05 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-26 19:05:01 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Fix addr_pfx test (749 bytes, patch) 2007-04-28 00:14 EDT, Herbert Xu	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Curtis Doty 2007-04-15 21:15:45 EDT

I don't understand why the bonding patch for bug #213559 also breaks the way
addr_pfx is set. This causes the interface to break as soon as xend is started.

Here's yet another way. Which also simplifes the setting of both vars in
get_ip_info() {
    addr_pfx=`ip -o addr show dev $1 |awk '$3=="inet"{print$4}'`
    gateway=`ip route show dev $1 |awk '/^default via/{print$3}'`
}

Comment 1 Herbert Xu 2007-04-28 00:14:43 EDT

Created attachment 153683 [details]
Fix addr_pfx test

Actually, the problem is that there is a test on the value of addr_pfx that
can't handle spaces.  This patch should fix the problem.

Comment 2 Red Hat Bugzilla 2007-07-24 20:07:44 EDT

change QA contact

Comment 3 Chris Lalancette 2008-02-26 19:05:01 EST

This report targets FC6, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.

Thanks

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