Description of problem: from: /etc/init.d/neutron-server reload() { restart } force_reload() { restart } restart() { stop start } stop() { echo -n $"Stopping $prog: " killproc -p $pidfile $prog retval=$? echo [ $retval -eq 0 ] && rm -f $lockfile return $retval } == While reloading the service, it will be stopped and then it wll get started. If its not possible to dynamically reload all configuration files for neutron-* related services then the "reload" option should be removed to avoid confusion. Version-Release number of selected component (if applicable): openstack-neutron-2013.2.3-14.el6ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: with the reload option, the service actually will get restarted. Expected results: If its not possible to dynamically reload all configuration files for neutron-* related services then the "reload" option should be removed to avoid confusion. Additional info:
Created attachment 1034617 [details] Change to all init scripts to remove reload action
rhel 6.6 Icehouse openstack (5) [root@puma07 ~]# neutron-server service reload usage: neutron-server [-h] [--config-dir DIR] [--config-file PATH] [--debug] [--log-config-append PATH] [--log-date-format DATE_FORMAT] [--log-dir LOG_DIR] [--log-file PATH] [--log-format FORMAT] [--nodebug] [--nouse-syslog] [--noverbose] [--state_path STATE_PATH] [--syslog-log-facility SYSLOG_LOG_FACILITY] [--use-syslog] [--verbose] [--version] neutron-server: error: unrecognized arguments: service reload from: /etc/init.d/neutron-server } restart() { stop start } reload() { restart } force_reload() { restart } openstack-neutron-2014.1.4-1.el6ost.noarch python-neutron-2014.1.4-1.el6ost.noarch openstack-neutron-ml2-2014.1.4-1.el6ost.noarch python-neutronclient-2.3.4-3.el6ost.noarch openstack-neutron-openvswitch-2014.1.4-1.el6ost.noarch
(In reply to Alexander Stafeyev from comment #7) > rhel 6.6 > Icehouse openstack (5) > > [root@puma07 ~]# neutron-server service reload > usage: neutron-server [-h] [--config-dir DIR] [--config-file PATH] [--debug] > [--log-config-append PATH] > [--log-date-format DATE_FORMAT] [--log-dir LOG_DIR] > [--log-file PATH] [--log-format FORMAT] [--nodebug] > [--nouse-syslog] [--noverbose] [--state_path > STATE_PATH] > [--syslog-log-facility SYSLOG_LOG_FACILITY] > [--use-syslog] [--verbose] [--version] > neutron-server: error: unrecognized arguments: service reload You swapped words :) It should be: service neutron-server reload neutron-server is an executable for spawning neutron-server process that is called from SysV script.
Tnx, [root@puma07 ~]# service neutron-server reload Stopping neutron: [ OK ] Starting neutron: [ OK ] Seems the option still exists
The reason is that older version openstack-neutron-2014.1.4-1.el6ost was used for this verification.
[root@puma09 ~]# rpm -qa |grep openstack-neutron openstack-neutron-ml2-2014.1.5-2.el6ost.noarch openstack-neutron-openvswitch-2014.1.5-2.el6ost.noarch openstack-neutron-2014.1.5-2.el6ost.noarch [root@puma09 ~]# service neutron-server reload Usage: /etc/init.d/neutron-server {start|stop|status|restart|condrestart|try-restart|force-reload}
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://rhn.redhat.com/errata/RHBA-2015-1755.html