Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515281 - unable to set up a VLAN [NEEDINFO]
Summary: unable to set up a VLAN
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1643104
TreeView+ depends on / blocked
 
Reported: 2017-11-20 13:50 UTC by Taft Sanders
Modified: 2019-03-28 15:05 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
fkrska: needinfo? (lnykryn)


Attachments (Terms of Use)

Description Taft Sanders 2017-11-20 13:50:09 UTC
Description of problem:
NetworkManager is not able to identify the network correctly if the NIC is tagged for a specific VLAN.

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

How reproducible:
Everytime

Steps to Reproduce:
1. Kickstart a RHEL 7.4 system with tagged nic
2.
3.

Actual results:
Network is unreachable

Expected results:
Connectivity

Additional info:

Comment 4 Lubomir Rintel 2017-11-22 16:45:53 UTC
This has nothing to do with NetworkManager, dracut hangs long before NetworkManager would ever get a chance to run. Reassigning.

Comment 5 Lukáš Nykrýn 2017-11-23 10:45:57 UTC
Can you please follow Troubleshooting part of man 8 dracut and post rdsosreport?

Comment 7 Taft Sanders 2018-09-05 12:49:14 UTC
Same issue exists in RHEL 7.5 as well

Comment 9 Lukáš Nykrýn 2019-03-28 15:05:29 UTC
After a subsystem meeting, we agreed that we are not able to fix this issue in 7.7 timeframe and it should be moved to 7.8, so let's remove the bug from RPL.


Note You need to log in before you can comment on or make changes to this bug.