Bug 1075126

Summary: Hosted Engine client fails if shared storage contains no data
Product: [Retired] oVirt Reporter: Greg Padgett <gpadgett>
Component: ovirt-hosted-engine-haAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, amureini, dfediuck, gklein, gpadgett, iheim, msivak, sbonazzo, yeylon
Target Milestone: ---   
Target Release: 3.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 13:36:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1047649, 1053040    

Description Greg Padgett 2014-03-11 14:37:28 UTC
Description of problem:
There are certain situations in which the Hosted Engine client API may be called when the HE shared storage contains no data.  In this case, the client API will fail with a message "Request failed: success".

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install hosted engine packages
2. Run hosted engine client API before hosted engine setup. (Alternatively, shut down hosted engine and wipe the shared metadata file on hosted engine's shared storage.  This will simulate a race where vdsm may query the storage using the HA client API before the storage is written to.)

The API can be used in a simple python script:
  import ovirt_hosted_engine_ha.client.client as haClient
  print haClient.HAClient().get_all_stats()


Actual results:
Error, "Request failed: success"

Expected results:
Empty but successful return from the api.

Additional info:

Comment 1 Sandro Bonazzola 2014-05-08 13:36:26 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.