Cause:
Too strict naming policy for VLAN names
Consequence:
if-down didn't work for descriptively-named interfaces
Fix:
Name format check removed
Result:
Now it works as expected
Description of problem:
/etc/sysconfig/network-scripts/ifdown-eth needs the same type of patch as ifup received as per bugs 462095/676708:
143c143
< if echo ${DEVICE} | LANG=C egrep -v '(:)' | LANG=C egrep -q '(eth|bond)[0-9]*\.[0-9][0-9]?[0-9]?[0-9]?' \
---
> if echo ${DEVICE} | LANG=C egrep -v '(:)' | LANG=C egrep -q '.+\.[0-9][0-9]?[0-9]?[0-9]?' \
The new initscripts rpm only patches ifup.
This supports functional/descriptive naming of interfaces (including biosdevname-style) where VLANs are used.
Without this patch, the vconfig rem is never called to remove the VLAN tag, leaving orphan VLAN config entries.
Version-Release number of selected component (if applicable):
All Redhat 5 and 6 with VLAN config support in ifup/ifdown-eth
How reproducible:
Every time.
Steps to Reproduce:
1. Confirm no VLAN tag set by cat /proc/net/vlan/config
2. Configure a VLAN interface on a descriptively named device, eg, "data.555" in ifcfg-data.555 and run "ifup data.555". (Requires current initscripts or manual edit to ifup.)
3. "ifdown data.555" (no errors reported)
4. See that VLAN 555 still present in /proc/net/vlan/config
Actual results:
VLAN 555 tag still in /proc/net/vlan/config, data.555@data device still exists.
Expected results:
VLAN 555 tag should be removed from /proc/net/vlan/config, and data.555@data devices does not exist.
Additional info:
Minor but easily fixed.
Created attachment 505314[details]
test patch
Just from reading the code, this seems far simpler than worrying about the device name.
Will require some testing on all the earlier releases. Does this work for you?
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
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-2013-0518.html
Description of problem: /etc/sysconfig/network-scripts/ifdown-eth needs the same type of patch as ifup received as per bugs 462095/676708: 143c143 < if echo ${DEVICE} | LANG=C egrep -v '(:)' | LANG=C egrep -q '(eth|bond)[0-9]*\.[0-9][0-9]?[0-9]?[0-9]?' \ --- > if echo ${DEVICE} | LANG=C egrep -v '(:)' | LANG=C egrep -q '.+\.[0-9][0-9]?[0-9]?[0-9]?' \ The new initscripts rpm only patches ifup. This supports functional/descriptive naming of interfaces (including biosdevname-style) where VLANs are used. Without this patch, the vconfig rem is never called to remove the VLAN tag, leaving orphan VLAN config entries. Version-Release number of selected component (if applicable): All Redhat 5 and 6 with VLAN config support in ifup/ifdown-eth How reproducible: Every time. Steps to Reproduce: 1. Confirm no VLAN tag set by cat /proc/net/vlan/config 2. Configure a VLAN interface on a descriptively named device, eg, "data.555" in ifcfg-data.555 and run "ifup data.555". (Requires current initscripts or manual edit to ifup.) 3. "ifdown data.555" (no errors reported) 4. See that VLAN 555 still present in /proc/net/vlan/config Actual results: VLAN 555 tag still in /proc/net/vlan/config, data.555@data device still exists. Expected results: VLAN 555 tag should be removed from /proc/net/vlan/config, and data.555@data devices does not exist. Additional info: Minor but easily fixed.