Bug 1352165

Summary: HE deployment cannot continue if glusterfs version does not match shared storage, and not clear error is captured in the Gluster cli log
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Kevin Hung <khung>
Component: Plugins.GlusterAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0.0.1CC: bugs, dfediuck, godas, sabose, tnisan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-22 06:50:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Hosted Engine setup log
none
Console output
none
Gluster cli.log none

Description Kevin Hung 2016-07-01 21:15:27 UTC 
Created attachment 1175101 [details]
Hosted Engine setup log

Description of problem:
The HE deployment gets stuck if the glusterfs version on the shared storage host is different from the version on the node. According to Sahina Bose @ RedHat [1], this is a compatibility issue on executing cli commands. --remote-host option throws errors when there's a version mismatch. The HE deployment should handle this error so that installation can proceed.

[1] http://lists.ovirt.org/pipermail/users/2016-July/040814.html

How reproducible:
Always

Steps to Reproduce:
1. Have a gluster server running a version of glusterfs not equal to 3.7.11.
2. Install a node using ovirt-node-ng-installer-ovirt-4.0-2016062412 ISO.
3. Go to https://<node>:9090/ and start HE deployment, or launch using ovirt-hosted-engine-setup.
4. Choose glusterfs as the shared storage.
5. At the prompt "Please specify the full shared storage connection path to use", enter a path to a gluster volume on the server in step 1.

Actual results:
The prompt will repeat. In the Cockpit portal, it returns a False value in the field. In the console, it will give the following error: [ ERROR ] Cannot access storage connection storage1.nullaxiom.com:/mgmttank: Command '/sbin/gluster' failed to execute

Expected results:
The installation should continue.

Additional info:
The setup log, console output, and cli.log are attached.
Comment 1 Kevin Hung 2016-07-01 21:16:24 UTC 
Created attachment 1175102 [details]
Console output
Comment 2 Kevin Hung 2016-07-01 21:16:56 UTC 
Created attachment 1175103 [details]
Gluster cli.log
Comment 3 Yaniv Lavi 2016-07-21 08:34:47 UTC 
*** Bug 1356210 has been marked as a duplicate of this bug. ***
Comment 4 Sahina Bose 2016-12-22 06:05:12 UTC 
To handle this better, --remote-host should be replaced with gluster rest APIs that will be available from glusterfs 4.0. Moving to 4.2 to match gluster release
Comment 5 Gobinda Das 2019-04-22 06:50:50 UTC 
Closing this as no action taken from long back.Please reopen if required.