Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1398042

Summary:	systemctl start network.service and or service network restart
Product:	Red Hat Enterprise Linux 7	Reporter:	jnikolak
Component:	doc-Networking_Guide	Assignee:	Mirek Jahoda <mjahoda>
Status:	CLOSED NOTABUG	QA Contact:	ecs-bugs
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	rhel-docs
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-22 00:36:01 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 jnikolak 2016-11-24 00:08:59 UTC

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

Describe the issue: 
If customer using NetworkManager to handle the network interface.

running older command such as 

service network.restart and or/
systemctl network.service 

will cause conflict as both services will be running.


Can we confirm if having both 
network.service and network.manager running will not cause any conflicts.
From what I understand it has been known to cause issues in the past before.

One item that seems to be missing from the documentation is 

networkmanager-wait-online 

This service appears to be required for the network to allocate ip's from my test.
Can we have some more information about that.

Comment 2 jnikolak 2016-12-22 00:36:01 UTC

there was a misunderstanding on my part, where service network restart and systemctl restart network.service are legacy commands that will restart interfaces that are not connected with Network manager.

service network restart and systemctl restart network.service can work in conjuction with NM and shouldn't cause any conflict.
If there is a conflict it needs to be troubleshooted per basis

This bugzilla can be closed after understanding this concept.