Bug 1147410

Summary: Stopping ovirt-ha-broker also crush ovirt-ha-agent
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-hosted-engine-haAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: dfediuck, ecohen, gchaplik, gklein, iheim, juwu, lsurette, mavital, sbonazzo, sherold
Target Milestone: ---Keywords: ZStream
Target Release: 3.4.3   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: ovirt-hosted-engine-ha-1.1.6-2.el6ev Doc Type: Bug Fix
Doc Text:
Previously, when stopping ovirt-ha-broker service on a host with the running engine virtual machine. The ovirt-ha-agent crashed and an engine virtual machine did not get started on another host. This bug updates the broker's notification system, and the engine virtual machine starts up as normal.
Story Points: ---
Clone Of: 1093646 Environment:
Last Closed: 2014-10-27 22:47:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1093646, 1099874, 1152564    
Bug Blocks:    
Attachments:
Description Flags
logs none

Comment 2 Artyom 2014-10-05 10:37:30 UTC
Checked on ovirt-hosted-engine-ha-1.1.6-1.el6ev.noarch
Stopping ovirt-ha-broker still also crush ovirt-ha-agent, vm still in state up, but from some reason score of second hosts drops to zero with "state=EngineUnexpectedlyDown"

Comment 3 Artyom 2014-10-05 10:41:22 UTC
Created attachment 943998 [details]
logs

Comment 5 Artyom 2014-10-19 14:44:16 UTC
Verified on ovirt-hosted-engine-ha-1.1.6-2.el6ev.noarch

Comment 7 errata-xmlrpc 2014-10-27 22:47:07 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://rhn.redhat.com/errata/RHBA-2014-1722.html