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 1156102

Summary: VLAN fails to initiliaze
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Jamrisko <tjamrisk>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: lnykryn, lpol, psklenar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:53:39 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:
Attachments:
Description Flags
Config files
none
Requested output
none
When PHYSDEV is not defined (different vlan) none

Description Tomas Jamrisko 2014-10-23 14:58:52 UTC
Created attachment 949963 [details]
Config files

Description of problem:
Networking stopped working after update from 7.0 to 7.1 nightly.
Trying ifup on the vlan devices ended with "PHYSDEV required". Specifying PHYSDEV resulted in a new error "Device not present".

Manually adding links for all vlans and then running ifup solved the issue (at least until reboot)

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

How reproducible:
(on my setup) 100% 

Steps to Reproduce:
1. Setup VLANs and try using them

Actual results:
They don't work.

Expected results:
They work.

Additional info:

Comment 2 Lukáš Nykrýn 2014-10-23 15:23:31 UTC
can you please try to put "set -x" to beginning of /etc/sysconfig/network-scripts/ifup 

than call the ifup on the device and post here the output?

Comment 3 Tomas Jamrisko 2014-10-23 15:56:37 UTC
Created attachment 950001 [details]
Requested output

Comment 4 Tomas Jamrisko 2014-10-24 07:40:39 UTC
Created attachment 950247 [details]
When PHYSDEV is not defined (different vlan)

Forgot to add the error when PHYSDEV is not specified..

Comment 5 Lukáš Nykrýn 2014-10-24 11:15:33 UTC
I haven't test it, but this should fix the issue:

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

Comment 8 Leos Pol 2015-01-07 12:29:16 UTC
initscripts-9.49.23-1.el7 contains fix from comment 5

Comment 10 errata-xmlrpc 2015-03-05 10:53:39 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.

https://rhn.redhat.com/errata/RHBA-2015-0471.html