Bug 1017406 - HA Agent should use startMonitoringDomain VDSM API for monitoring hosted engine storage domain
Summary: HA Agent should use startMonitoringDomain VDSM API for monitoring hosted engi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-ha
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.3.0
Assignee: Greg Padgett
QA Contact: Artyom
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-09 19:56 UTC by Greg Padgett
Modified: 2016-06-12 23:16 UTC (History)
9 users (show)

Fixed In Version: ovirt-hosted-engine-ha-0.1.0-0.3.1.beta1.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 16:50:45 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0080 0 normal SHIPPED_LIVE new package: ovirt-hosted-engine-ha 2014-01-21 21:00:07 UTC
oVirt gerrit 20051 0 None None None Never

Description Greg Padgett 2013-10-09 19:56:20 UTC
(See bug 1015136 for tracking of same issue in ovirt-hosted-engine-setup.)

Use startMonitoringDomain VDSM API for monitoring hosted engine storage domain.

API introduced with upstream patch: http://gerrit.ovirt.org/#/c/19762/ .

Comment 1 Greg Padgett 2013-10-15 12:53:50 UTC
Merged Change-Id: I9bab369784fecbf972622922a925fd0b45de123f

Comment 3 Ilanit Stein 2013-10-27 14:44:50 UTC
Can you please explain how this bug can be verified?
thanks.

Comment 4 Greg Padgett 2013-10-27 21:57:54 UTC
If it works, you should see 2 things:

 a) /var/log/ovirt-hosted-engine-ha/agent.log will show something like:
   "Started VDSM domain monitor for <domain uuid>"

 b) After the agent has started the monitor (seen in step a), running 'vdsClient [-s] 0 repoStats' will show the sd (same uuid as above) with an "acquired: True" state

Comment 5 Artyom 2013-10-28 13:50:57 UTC
Verified on ovirt-hosted-engine-ha-0.1.0-0.3.1.beta1.el6ev
In agent.log appear "VDSM is monitoring domain ff5d4d84-ec91-4662-9259-c7ae3d1bf6bc"
Via vdsClient -s 0 repoStats I see the same domain uuid:
Domain ff5d4d84-ec91-4662-9259-c7ae3d1bf6bc {'code': 0, 'version': 3, 'acquired': True, 'delay': '0.000360647', 'lastCheck': '9.0', 'valid': True}

Comment 6 Charlie 2013-11-28 01:42:17 UTC
This bug is currently attached to errata RHEA-2013:15591. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 7 Greg Padgett 2013-12-06 18:00:40 UTC
ovirt-hosted-engine-ha is a new package; does not need errata for bugs during its development.

Comment 8 errata-xmlrpc 2014-01-21 16:50:45 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.

http://rhn.redhat.com/errata/RHEA-2014-0080.html


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