Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1116394

Summary: Vlans doesn't start because regression in initscipts.
Product: Red Hat Enterprise Linux 6 Reporter: Robin Hack <rhack>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: high Docs Contact:
Priority: high    
Version: 6.6CC: jscotka, psklenar, tlavigne
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: initscripts-9.03.46-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1175392 (view as bug list) Environment:
Last Closed: 2014-10-14 06:28:42 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1175392    
Attachments:
Description Flags
ifup 6.5 vs 6.6 diff none

Description Robin Hack 2014-07-04 12:44:46 UTC
Description of problem:
Hi.

I have some servers with rhel6.6 where vlan is configured via ifup scripts.
# cat /etc/sysconfig/network-scripts/ifcfg-vlan178 
DEVICE=vlan178
VLAN=yes
VLAN_NAME_TYPE=VLAN_PLUS_VID_NO_PAD
PHYSDEV=em1
BOOTPROTO=static
ONBOOT=yes
BRIDGE=br0_vlan178

Bridge is running without problems.

Version-Release number of selected component (if applicable):
initscripts-9.03.44-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. setup vlan script
2. shutdown networkmanager
3. ifup vlan178

Actual results:
Device vlan178 does not seem to be present, delaying initialization.

Expected results:
vlan up and running

Additional info:
Main trouble is hidden in /etc/sysconfig/network-scripts/ifup. I did diff a and just vlan part is modified. I'm able to workaround this by replacing ifup script from rhel 6.5.

Comment 1 Petr Sklenar 2014-07-04 12:53:05 UTC
FYI this bug was introduced by upgrading from rhel65 (where it works) to rhel66nightly.

Comment 2 Robin Hack 2014-07-04 12:55:50 UTC
Created attachment 914716 [details]
ifup 6.5 vs 6.6 diff

Diff of 6.5 and 6.6 ifup script.

Comment 4 Lukáš Nykrýn 2014-07-07 14:33:00 UTC
diff --git a/sysconfig/network-scripts/ifup b/sysconfig/network-scripts/ifup
index 910b105..189fcce 100755
--- a/sysconfig/network-scripts/ifup
+++ b/sysconfig/network-scripts/ifup
@@ -72,7 +72,7 @@ fi
 
 # Ethernet 802.1Q VLAN support
 if [ "${VLAN}" = "yes" ] && [ "$ISALIAS" = "no" ] && [ -n $DEVICE ]; then
-    if [ -n ${VID} ]; then
+    if [ -n "${VID}" ]; then
         if test -z "$PHYSDEV"; then
             net_log $"PHYSDEV should be set for device ${DEVICE}"
             exit 1

This should fix the issue

Comment 7 Lukáš Nykrýn 2014-07-22 14:12:30 UTC
*** Bug 1120252 has been marked as a duplicate of this bug. ***

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