Description of problem: In 3.0, one could have performed 'service jbossas restart' to restart the service. In 3.1, it's not available: service ovirt-engine restart Usage: engine-service.py {start|stop|status} (also notice that the usage refers to 'engine-service.py', but that's a different bug). The restart is requested after making changes via rhevm-manage-domains: "Successfully added domain qa.lab.tlv.redhat.com. oVirt Engine restart is required in order for the changes to take place (service ovirt-engine restart)." Version-Release number of selected component (if applicable): rhevm-setup-3.1.0_0001-14.el6ev.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 833305 has been marked as a duplicate of this bug. ***
The fix for this bug is included in the following change: http://gerrit.ovirt.org/#/c/5355 This is how the output of the script looks like after the change (it uses colors, but that is not visible here): # service ovirt-engine Usage: engine-service {start|stop|restart|status} # service ovirt-engine start Starting engine-service: [ OK ] # service ovirt-engine stop Stopping engine-service: [ OK ] # service ovirt-engine restart Stopping engine-service: [ OK ] Starting engine-service: [ OK ] It will show FAILED instead of OK if something goes wrong. Additional information will be sent to syslog (/var/log/messages).
This change has been merged: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=0ec7ac2541783b4bf7353a0303c8a5938ed4ed13
verified on si13: [root@hateya-rhevm ~]# /etc/init.d/ovirt-engine Usage: engine-service {start|stop|restart|status} verified that restart indeed works.