Hide Forgot
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.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/123
fixed upstream.
covered by new version of @vlan_on_bond_autoconnect https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/commit/7bba94ee52fa9865f8d2e83e27081cd3a68999e3
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