Description of problem: Can not create a new geo replication due to a bug in vdsm. Tested on Centos 7.3 but from what i have found it should be affected on all linux distributions. Version-Release number of selected component (if applicable): vdsm 4.19.10 in ovirt release 4.1.1 How reproducible: Setup a new system with two clusters with gluster. Go to one storage volume and start creating geo replication. It wont give you any volume to replcate to even if they do exist. If one try to do it manually and force a replcation it will say that the volume is not empty. After some digging around in the logs i did find that it complains on a python module. I fixed it by a change in this file: /usr/lib/python2.7/site-packages/vdsm/gluster/gfapi.py Change row 252 from: module = "gluster.gfapi" to module = "vdsm.gluster.gfapi" Then it almost works as it should. But i still cant click on the ok button to finish the creation of the geo replicated volume nothing happens. So it must be an additional problem as well Actual results: First "volume not empty" error. But after fixing gfapi.py the ok button still wont work. Expected results: Creation of a geo replicated volume. Additional info:
Apparently the gfapi.py was fixed in #1409052 but i did not find it at first. And it is not available on the centos 7.3 packages yet. But still cant click on ok to finalize the the creation of the geo replicated volume
This was a UI issue on validation. If the checkbox "Show volumes eligible for geo-replication" is unchecked, the list of volumes is populated. When a volume is selected, the reasons why the volume is not eligible is listed. If user wishes to, they can go ahead and create the session ignoring these warnings.
Tested with RHV-4.1.2.2 Verified that the issue is no longer observed with the following steps 1. Created 2 gluster clusters and added gluster nodes 2. Created a volume in each cluster. 3. When selecting the volume, and creating geo-replication, it lists the available volume in the other cluster. 4. Created the geo-replication session and started the sync, observed that all the files are synced