Bug 1398769 - Unable to deploy host in degraded Gluster scenario
Summary: Unable to deploy host in degraded Gluster scenario
Keywords:
Status: CLOSED DUPLICATE of bug 1404606
Alias: None
Product: ovirt-host-deploy
Classification: oVirt
Component: Plugins.Hosted-Engine
Version: master
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-25 21:33 UTC by Kevin Hung
Modified: 2016-12-22 08:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-22 08:11:04 UTC
oVirt Team: Gluster
Embargoed:
sabose: ovirt-4.2?
sabose: planning_ack?
sabose: devel_ack?
sabose: testing_ack?


Attachments (Terms of Use)

Description Kevin Hung 2016-11-25 21:33:54 UTC
Description of problem:
Specifying an unavailable shared storage connection path causes hosted-engine --deploy to fail even if we pass in a backup volfile server using --config-append.

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

How reproducible:
Always

Steps to Reproduce:
1. Bring down a Gluster server (storage1) that's part of a replica 3 or greater volume.
2. Log onto the host that we will be deploying.
3. Create a config file append.conf with the following text:
[environment:default]
OVEHOSTED_STORAGE/mntOptions=str:backup-volfile-servers=storage2:storage3
4. hosted-engine --deploy --config-append=append.conf
5. For storage type, enter 'glusterfs'
6. For shared storage connection path, enter 'storage1:/mgmttank'

Actual results:
Script returns an error about not being able to connect.
2016-11-25 15:31:58 DEBUG otopi.plugins.gr_he_setup.storage.nfs plugin.execute:921 execute-output: ('/sbin/gluster', '--mode=script', '--xml', 'volume', 'info', 'mgmttank', '--remote-host=storage1') stdout:
Connection failed. Please check if gluster daemon is operational.

Expected results:
Script should try the servers listed in the mount option 'backup-volfile-servers' or 'backupvolfile-server' and continue if successful.

Additional info:
I do not believe that 'gluster volume info' takes the arguments 'backup-volfile-servers' or 'backup-volfile-server'. However, oVirt should be able to parse the information and try to connect.

Comment 1 Sahina Bose 2016-12-22 08:11:04 UTC
Closing this as duplicate of Bug 1404606 as it has more information related to the same issue

*** This bug has been marked as a duplicate of bug 1404606 ***


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