Bug 713757
| Summary: | ifup script can't reconize bridge device name "brbond0.XX" | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Teruaki Ishizaki <teruaki.ishizaki> | |
| Component: | initscripts | Assignee: | Lukáš Nykrýn <lnykryn> | |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.1 | CC: | azelinka, jscotka, lnykryn, myamazak, notting, ovasik, tichikawa, vpavlin, ykawada | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | initscripts-9.03.32-1.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
Previous version of sysconfig.txt led users to put VLAN=yes in global config file.
Consequence:
Interface with name containing dot (brbond0.XX) are recognized as VLAN interfaces.
Fix:
Sysconfig.txt was changed - VLAN stanza belongs to interface config file.
Result:
Mentioned devices are no longer recognized as VLAN interfaces.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 860252 (view as bug list) | Environment: | ||
| Last Closed: | 2013-02-21 10:25:21 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
typo: >we create a file /etc/sysconfig/network-scripts/ifcfg-brbond0.XX >---------------------------- >DEVICE=brbond0.XX >TYPE=Bridge >BOOTPROTO=none >ONBOOT=yes >USERCTL=no >IPADDR=AA.BB.CC.DD >NETMASK=255.255.255.0 >DELAY=0 >----------------------------- > >and /etc/sysconfig/ifcfg-bond0.XX. and /etc/sysconfig/network-scripts/ifcfg-bond0.XX How does it fail? How much of the stack is set up? Out of curiosity, does reverting: http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=f1db9810c3fda50c887e33e83e80f767476dd446 and http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=368c219887e76664b8c3a374c9dd3086d0078759 help? I think those patches makes those problem. Our system is using that naming convention "brbond0.XX" for bridge device. Naming convention's change between RHEL versions have a great influence on existing system. Naming default policy is exist?(vlan, bonding, bridge, ...etc) (In reply to comment #5) > I think those patches makes those problem. I'm sorry, I don't quite understand you hear. Are you saying that removing these changes fixes the issue for you? That should be 'understand you here'. Also, when it's not working for you, how far does it get? Which of the component devices are set up correctly? (In reply to comment #6) > (In reply to comment #5) > > I think those patches makes those problem. > > I'm sorry, I don't quite understand you hear. Are you saying that removing > these changes fixes the issue for you? I think that these changes fix the issue. Brbond0.XX is misunderstanded for VLAN device with initscripts-9.03.23-1.el6. I tested changing bridge name to brbond0_XX or brbond0-XX, and bridge interface was up successfully.(using initscripts-9.03.23-1.el6) 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.
It seems weird to me that these two patches broke it. First one looks really harmless and the second one is "used" only in case that there is VLAN=yes in configuration file. This is probably caused by setting VLAN=yes in sysconfig/network. Then this variable has the same value in ifup script. Obvious workaround for this would be to explicitly set VLAN=no in ifcfg-brbond0.XX.
Solution to this would be to unset VLAN after sourcing sysconfig/network, but I am not sure if this is completely correct.
--- a/sysconfig/network-scripts/ifup
+++ b/sysconfig/network-scripts/ifup
@@ -23,6 +23,7 @@ cd /etc/sysconfig/network-scripts
. ./network-functions
[ -f ../network ] && . ../network
+unset VLAN #we want check VLAN in device config
CONFIG=${1}
Might be simplest to fix the docs to say that VLAN should be set in the config file, not /etc/sysconfig/network. Fixed in upstream sysconfig.txt, at least. But this variable is also used in init.d/network script, where it starts modprobe 8021q. Right, but since it's also loaded in ifup, so I don't think that stanza of init.d/network is actually needed. Did I miss a usage case here? My mistake, I overlooked the modprobe in ifup. I'm troubled, too.
I want VLAN Interface to Bridge (to use KVM vnetXX).
bond0 --[bridge]--> br0
|
[vlan]
|
bond0.xx --[bridge]--> br0.xx
/sbin/ifup
- MATCH='^(eth|hsi|bond)[0-9]+\.[0-9]{1,4}$'
+ MATCH='^.+\.[0-9]{1,4}$'
In old script, br0.xx is normal interface up.
That not VLAN, but success bridge VLAN bond0.xx.
But, in new script, br0.xx to up VLAN (on VLAN, doubled).
then "ERROR: could not add vlan XX as br0.XX on dev br0" displayed.
I suppose when ifup "TYPE=Bridge" interface except to VLAN mode.
I am afraid that I don't understand you completely and not sure how this change could cause this error. Are you sure you have VLAN=yes set only in ifcfg for VLAN interfaces? Oh! I've defined 'VLAN=yes' in [/etc/sysconfig/network]. I understand. thanks. I will define it in every [/etc/sysconfig/network-scripts/ifcfg-*.xxx], really wants to up to VLAN. (but... it's so many files...) Don't forget to remove 'VLAN=yes' from [/etc/sysconfig/network]. 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: ifup script can't reconize bridge device name "brbond0.XX" from initscripts-9.03.23-1.el6. our NW stack is below eth0 --- |--- bond0 --- bond0.XX --- brbond0.XX eth1 --- we create a file /etc/sysconfig/network-scripts/ifcfg-brbond0.XX ---------------------------- DEVICE=brbond0.XX TYPE=Bridge BOOTPROTO=none ONBOOT=yes USERCTL=no IPADDR=AA.BB.CC.DD NETMASK=255.255.255.0 DELAY=0 ----------------------------- and /etc/sysconfig/ifcfg-bond0.XX. Start OS, but brbond0.XX device status is not up. If we use initscripts-9.03.17-1.el6, brbond0.XX device is successfully up. Version-Release number of selected component (if applicable): initscripts-9.03.23-1.el6 Steps to Reproduce: 1.create ifcfg-bond0.XX file for vlan device 2.create ifcfg-brbond0.XX file for bridge device connecting to bond0.XX 3.reboot or /etc/init.d/network start Actual results: brbond0.XX is not up. Expected results: brbond0.XX is up. Additional info: If we use initscripts-9.03.17-1.el6, brbond0.XX device is successfully up.