Bug 1317081

Summary:	instructions for applying profile changes
Product:	Red Hat Enterprise Linux 7	Reporter:	Pete Travis <me>
Component:	doc-Networking_Guide	Assignee:	Mirek Jahoda <mjahoda>
Status:	CLOSED NOTABUG	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	lrintel, mjahoda, rhel-docs
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-22 15:18:04 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:

Description Pete Travis 2016-03-11 22:24:52 UTC

Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html

Section Number and Name: 2.3. Using the NetworkManager Command Line Tool, nmcli

Describe the issue: 

I've found that both `nmcli con reload $ifname` and `nmcli con up $ifname` are required for changes made via `nmcli con modify` or `nmcli con edit` to take effect.   The nmcli usage guide implies this, but does not explicitly state it.

Suggestions for improvement: 

Add a small subsection along the lines of "to apply your changes, do..."

Additional information: 
This isn't rigorously tested, but the above process was definitely required when adding an IP address.

Comment 5 Mirek Jahoda 2016-06-22 15:18:04 UTC

   Hello,

from what I know, it works this way:

- if you made changes via "nmcli con edit" or "nmcli con modify" then you need only to run "nmcli con up $conname"
- if you manually edit ifcfg files (/etc/sysconfig/network-scripts/ifcfg-*) then you have to load them in the memory by running the "nmcli con reload $conname" command and bring up the connection again additionally

The Networking Guide does not need any correction in this case. I will close the bug for now, if you can reproduce this please reopen the bug, describe the steps, and provide NetworkManager version.

Kind regards,
--Mirek