+++ This bug was initially created as a clone of Bug #1047649 +++ (Cloned for submission of a new ha client api needed to properly read local host's ha status from the ha client.) Description of problem: Currently hosted engine has its own flows to maintenance the engine VM and another flow to maintenance an HA-enabled host. These flows should be unified with the existing host maintenance flows. --- Additional comment from Doron Fediuck on 2014-01-01 09:23:55 EST --- This BZ was created for the engine side, but another may be needed for VDSM to support HA-maintenance request from the engine. --- Additional comment from Itamar Heim on 2014-01-12 03:42:42 EST --- setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
Added a get_local_host_id() method to the ha client api. For testing, if the HA status shows up in webadmin for a host on which it is configured, then this API is working.
Hi Greg, can you say the best way to verify this bug. Thanks
(In reply to Artyom from comment #2) > Hi Greg, can you say the best way to verify this bug. > Thanks Hi Artyom. Currently, you can check the ovirt-hosted-engine-ha changes by calling the new api with a short python script on a node in the ha cluster. Something like this would work, and if it returns the host id, then this paticular bug/patch is working: import ovirt_hosted_engine_ha.client.client as haClient print haClient.HAClient().get_local_host_id() Once all other patches for this feature are merged (see bug 1047649 and bug 1053040) then this will be testable as part of the overall feature--if the feature works in the engine UI, then this bug/patch works as well.
Thanks a lot verified on ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch
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/RHBA-2014-0671.html