Hide Forgot
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.
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.