Bug 832782 - ovirt-engine-setup: "ovirt-engine restart" is missing
Summary: ovirt-engine-setup: "ovirt-engine restart" is missing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.1.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Yaniv Kaul
URL:
Whiteboard: integration
: 833305 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-17 11:18 UTC by Yaniv Kaul
Modified: 2015-09-22 13:10 UTC (History)
9 users (show)

Fixed In Version: si10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:03:57 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yaniv Kaul 2012-06-17 11:18:32 UTC
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:

Comment 2 Yaniv Kaul 2012-06-19 08:28:41 UTC
*** Bug 833305 has been marked as a duplicate of this bug. ***

Comment 3 Juan Hernández 2012-06-21 15:51:48 UTC
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).

Comment 5 Haim 2012-08-07 06:17:45 UTC
verified on si13:


[root@hateya-rhevm ~]# /etc/init.d/ovirt-engine 
Usage: engine-service {start|stop|restart|status}

verified that restart indeed works.


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