Description of problem: Creating this bug for pushing changes to dist-git as it requires at least one bz with properly ack'ed.
For the following features, VDSM changes are coming in, which will be merged downstream dist-git 1164108-[RFE] Enable provisioning and discovery of disks to use as gluster bricks 1083574 - [RFE] Manage gluster volume snapshot 1125845 - [RFE] Support management of gluster geo-replication session from oVirt 1179074 - [RFE] Support RDMA transport type while creating/displaying gluster volumes 1049994 - [RFE][HC] - Allow choosing network interface for gluster domain traffic
Closing this bug as it was used for initial 3.1 vdsm build. Any new vdsm changes should use the corresponding acked bug
(In reply to Sahina Bose from comment #4) > Closing this bug as it was used for initial 3.1 vdsm build. Any new vdsm > changes should use the corresponding acked bug The 3.1 vdsm build is not available at the current release which at this point of time is RHGS 3.0 Update 4 Please keep this BZ open till RHGS 3.1 release
But should we be using a generic bug that cannot be verified to push changes? I think it's appropriate to use actual bugs if patches need to be pushed. Maybe the bug needs to be CLOSED with an appropriate status (rather than CURRENTRELEASE)
Moving back to MODIFIED as the build is not ready but errata has moved the bugs to ON_QA.
VDSM build is ready for testing.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html