Bug 1554690 - systemctl reload network.service is failing
Summary: systemctl reload network.service is failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Kaspar [Dee'Kej]
QA Contact: Daniel Rusek
Ioanna Gkioka
URL:
Whiteboard:
Depends On:
Blocks: 1561087
TreeView+ depends on / blocked
 
Reported: 2018-03-13 07:56 UTC by Fani Orestiadou
Modified: 2018-10-30 10:17 UTC (History)
5 users (show)

Fixed In Version: initscripts-9.49.42-1.el7
Doc Type: Bug Fix
Doc Text:
A non-functioning "systemctl reload network.service" has been removed The "systemctl reload network.service" command, which does not work due to technical limitations of initscripts has been removed, and using it now results in an appropriate warning message. To correctly apply a new configuration for the network service, use the "restart" command instead: ~]# systemctl restart network.service
Clone Of:
: 1561087 (view as bug list)
Environment:
Last Closed: 2018-10-30 10:15:57 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3131 None None None 2018-10-30 10:17:17 UTC

Description Fani Orestiadou 2018-03-13 07:56:23 UTC
Description of problem:

Reload the network service is producing "Job for network.service canceled." and leaves the service in inactive state.

# systemctl status network
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: inactive (dead) since Tue 2018-03-13 08:46:44 CET; 3min 30s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 32088 ExecReload=/etc/rc.d/init.d/network reload (code=killed, signal=TERM)
  Process: 829 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)

Mar 13 08:46:44 fvm-rhel-7-4-215 network[32088]: Stopping network (via systemctl):
Mar 13 08:46:44 fvm-rhel-7-4-215 systemd[1]: Stopped LSB: Bring up/down networking.
Mar 13 08:49:49 fvm-rhel-7-4-215 systemd[1]: Unit network.service cannot be reloaded because it is inactive.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.


I am not quite sure what is the exact purpose of the reload feature for the networking service, but since is present, i would expect it to work. Checking the code, it seems to me like it should produce the exact result as "systemctl restart network" 

less /etc/rc.d/init.d/network

...

restart|reload|force-reload)    <---
    cd "$CWD"
    $0 stop
    $0 start
    rc=$?
    ;;
*)
    echo $"Usage: $0 {start|stop|status|restart|reload|force-reload}"
    exit 2
esac

exit $rc

Same result when you try to reload by the script itself 

# /etc/rc.d/init.d/network reload
Reloading network configuration (via systemctl):  Job for network.service invalid.
                                                           [FAILED]

Version-Release number of selected component (if applicable):
Tested with 
initscripts-9.49.39-1.el7.x86_64
initscripts-9.49.41-1.el7.x86_64

initscripts-9.49.30-1.el7_2.2.x86_64

How reproducible:
Reload of the service

Steps to Reproduce:
1. systemctl reload network 
2.
3.

Actual results:
# systemctl reload network 
Job for network.service invalid.


Expected results:
Network service should be restarted 

Additional info:
- 

Let me know whether more details are needed. 
Thank you

Comment 2 David Kaspar [Dee'Kej] 2018-03-13 11:54:35 UTC
Hello Fani! :)

The 'reload' and 'force-reload' are "leftovers" in initscripts by mistake. These commands won't work  for network service at all, and this can't be technically fixed in any reasonable way...

We will remove these commands from the network service, so it is no longer confusing our customers and causing this issue.

Fani, please, let our customers know the 'reload' and 'force-reload' are not working.

However, it would be nice if we would have a KB article for this as well. I'm adding Lenka to CC for this. Lenka, could somebody from your Doc Team get in contact with me, so we can write this KB article? :) Thanks!

Comment 3 Lenka Špačková 2018-03-13 12:50:52 UTC
Hi David, 
I suggest Ioanna, the networking docs specialist. Ioanna, could you get in touch with David and help him?
Thanks a lot!

Comment 4 Fani Orestiadou 2018-03-13 13:33:39 UTC
Hello David, 

Thank you very much for your fast response. I will create a KCS article and i will be in contact with Ioanna as well for our official docs.   

Fani

Comment 19 errata-xmlrpc 2018-10-30 10:15:57 UTC
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-2018:3131


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