Gluster 3.10 has been released, we need to make sure vdsm works with it.
Saw 3.11 released (but is it available in CentOS repos already?)
(In reply to Yaniv Kaul from comment #1) > Saw 3.11 released (but is it available in CentOS repos already?) Currently in testing: http://cbs.centos.org/koji/buildinfo?buildID=17276
(In reply to Sandro Bonazzola from comment #2) > (In reply to Yaniv Kaul from comment #1) > > Saw 3.11 released (but is it available in CentOS repos already?) > > Currently in testing: http://cbs.centos.org/koji/buildinfo?buildID=17276 gluster 3.11 is a Short term release - will not be published to Centos repo
(In reply to Sahina Bose from comment #3) > (In reply to Sandro Bonazzola from comment #2) > > (In reply to Yaniv Kaul from comment #1) > > > Saw 3.11 released (but is it available in CentOS repos already?) > > > > Currently in testing: http://cbs.centos.org/koji/buildinfo?buildID=17276 > > gluster 3.11 is a Short term release - will not be published to Centos repo So we need to consider to stay on 3.10 for 4.2 or target 3.12. We need to check schedule for 3.12 to be compatible with oVirt 4.2 planning.
Sahina, what's the plan with Gluster? Should we stay on 3.10 or point to 3.12 since it's now available?
We need to move to 3.12
Verified that VDSM works well with glusterfs-3.12
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.