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 1701585 - nmcli does not bring up vlan interfaces
Summary: nmcli does not bring up vlan interfaces
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.7
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-19 17:36 UTC by suresh kumar
Modified: 2019-08-06 13:17 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.18.0-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:16:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2302 0 None None None 2019-08-06 13:17:10 UTC

Description suresh kumar 2019-04-19 17:36:06 UTC 
Description of problem:

Customer has a requirement of restarting NetworkManager. But it created issues like creating duplicate policy rules for every restart. So we suggested below method to restart NetworkManager


nmcli networking off
systemctl restart NetworkManager
nmcli networking on


But this does not bring up vlan interfaces:


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

 NetworkManager-1.12.0-10.el7_6.x86_64.


How reproducible:
 Always


Steps to Reproduce:

# cat ifcfg-eth0.10 
TYPE="Vlan"
PHYSDEV="eth0"
ONBOOT="yes"
IPADDR=192.168.123.102
NETMASK=255.255.255.0
VLAN="yes"
VLAN_ID=10
NAME=eth0.10


//Before:
# nmcli co show
NAME     UUID                                  TYPE      DEVICE  
eth0     5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0    
eth0.10  2dadfa26-8bfc-790a-38d4-6a0151de29d3  vlan      eth0.10 


# nmcli networking off;systemctl restart NetworkManager; nmcli networking on

//Now
# nmcli co show
NAME     UUID                                  TYPE      DEVICE 
eth0     5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03  ethernet  eth0   
eth0.10  2dadfa26-8bfc-790a-38d4-6a0151de29d3  vlan      --     <<<<<



Actual results:
nmcli  does not bring up vlan interface.

Expected results:
nmcli bring up vlan interface.
Comment 2 Beniamino Galvani 2019-04-29 09:18:56 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/123
Comment 3 Thomas Haller 2019-05-01 13:05:54 UTC 
fixed upstream.
Comment 6 Vladimir Benes 2019-05-17 08:57:25 UTC 
covered by new version of @vlan_on_bond_autoconnect
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/commit/7bba94ee52fa9865f8d2e83e27081cd3a68999e3
Comment 8 errata-xmlrpc 2019-08-06 13:16:56 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://access.redhat.com/errata/RHBA-2019:2302
Note You need to log in before you can comment on or make changes to this bug.