Description of problem: The volume info currently lists n-1 servers as backupvolfile-servers. The backupvolfile-server mount option expects only one value, and not a comma-separated set of values. Version-Release number of selected component (if applicable): heketi-devel-1.0.0-1.el7rhgs.noarch How reproducible: Always Steps to Reproduce: 1. Create a heketi volume 2. The output of a volume creation command successfully executed has the mount options value 3. Actual results: Mount Options: backupvolfile-servers=rhshdp03.lab.eng.blr.redhat.com,rhshdp04.lab.eng.blr.redhat.com,rhshdp06.lab.eng.blr.redhat.com,rhshdp13.lab.eng.blr.redhat.com When I try to mount it, I get the following error: mount -t glusterfs -o backupvolfile-server=rhshdp03.lab.eng.blr.redhat.com,rhshdp04.lab.eng.blr.redhat.com,rhshdp06.lab.eng.blr.redhat.com,rhshdp13.lab.eng.blr.redhat.com rhshdp05.lab.eng.blr.redhat.com:vol_20363034cdd3439f675d6db92da6bb3b /mnt/ Invalid option rhshdp04.lab.eng.blr.redhat.com
Anush, Since this is an interface to services and not to users, Heketi provides services with all possible choices for backupvolfile-servers. It is up to the service to show the user the correct service choice. Does that make sense?
(In reply to Luis Pabón from comment #2) > Anush, Since this is an interface to services and not to users, Heketi > provides services with all possible choices for backupvolfile-servers. It is > up to the service to show the user the correct service choice. > > Does that make sense? It does, though it would be useful to just pull it off as is to run a mount command. Also, the output format is similar to the mount option syntax. So it could be confusing unless we clearly mention it?
Updated the API spec file. https://github.com/heketi/heketi/wiki/API#volume_info
Marking this as verified.