oVirt 4.1.z has glusterfs 3.8 as supported version and is going to have ansible 2.4.0.0 inherited from Fedora / EPEL / CentOS PaaS SIG. Please check gdeploy still works with ansible 2.4.0.0, I don't expect regression, but just to be sure...
Please report this as a new issue against gdeploy itself: https://github.com/gluster/gdeploy/issues Note that glusterfs-3.8 does not get any further updates, and is end-of-life. I recommend you move to glusterfs-3.10 or glusterfs-3.12 as soon as possible.
(In reply to Niels de Vos from comment #1) > Please report this as a new issue against gdeploy itself: > > https://github.com/gluster/gdeploy/issues I'll do > Note that glusterfs-3.8 does not get any further updates, and is > end-of-life. I recommend you move to glusterfs-3.10 or glusterfs-3.12 as > soon as possible. Sahina, if we need to switch to 3.10 or 3.12 in oVirt 4.1.z please open a BZ for it. Right now we are targeting 3.12 on oVirt 4.2 only.
(In reply to Sandro Bonazzola from comment #2) > (In reply to Niels de Vos from comment #1) > > Please report this as a new issue against gdeploy itself: > > > > https://github.com/gluster/gdeploy/issues > > I'll do > > > Note that glusterfs-3.8 does not get any further updates, and is > > end-of-life. I recommend you move to glusterfs-3.10 or glusterfs-3.12 as > > soon as possible. > > Sahina, if we need to switch to 3.10 or 3.12 in oVirt 4.1.z please open a BZ > for it. Right now we are targeting 3.12 on oVirt 4.2 only. I think 3.8 is ok for 4.1.z as switching this would mean a mismatch in upstream and downstream versions.