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 1317081 - instructions for applying profile changes
Summary: instructions for applying profile changes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Networking_Guide
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Mirek Jahoda
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-11 22:24 UTC by Pete Travis
Modified: 2019-03-06 00:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-22 15:18:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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