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.
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 ***