Bug 1082765

Summary: Allow AGEING to be set in ifcfg-* scripts
Product: Red Hat Enterprise Linux 6 Reporter: James W. Mills <jamills>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: low Docs Contact:
Priority: low    
Version: 6.6CC: psklenar
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: initscripts-9.03.42-1.el6 Doc Type: Bug Fix
Doc Text:
Already covered in different bug.
Story Points: ---
Clone Of:
: 1083211 (view as bug list) Environment:
Last Closed: 2014-10-14 06:28:17 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:
Bug Depends On:    
Bug Blocks: 1083211, 1083694    

Description James W. Mills 2014-03-31 19:10:56 UTC
Description of problem:

We need to allow ageing to be set in ifcfg-* scripts

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

RHEL 6.x

How reproducible:

100%

Steps to Reproduce:

Add "AGEING=0" to an ifcfg-* file that is a bridge


Actual results:

No change in aging value when you run "brctl showstp <bridge>"

Expected results:

"brctl showstp <bridge>" shows "max age		  0.00"

Additional info:

A recent problem with internal blade switches not forwarding traffic led us to needing to disable ageing completely.  This method for manipulating the ageing of the bridge is much preferable to a standalone script executed after the interface is already up.

There is an upstream patch for this already:

https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=81143a44c2f3b11a7a70a48d909e831c8cd3a79f

Comment 5 errata-xmlrpc 2014-10-14 06:28:17 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.

http://rhn.redhat.com/errata/RHBA-2014-1448.html