+++ This bug was initially created as a clone of Bug #1491292 +++ Description of problem: Currently only volume name is sent as part of VOLUME_CREATE event. It would be very helpful if we can get the list of bricks with which volume was created along with the event Version-Release number of selected component (if applicable): 3.12 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18306 (events : Add brick list in EVENT_VOLUME_CREATE) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: https://review.gluster.org/18306 (events : Add brick list in EVENT_VOLUME_CREATE) posted (#2) for review on master by Atin Mukherjee (amukherj)
COMMIT: https://review.gluster.org/18306 committed in master by Atin Mukherjee (amukherj) ------ commit f6775423d7fbe71fe35e6154388e77aae2e264ad Author: Atin Mukherjee <amukherj> Date: Fri Sep 15 19:01:53 2017 +0530 events : Add brick list in EVENT_VOLUME_CREATE Change-Id: Ibf87ae5ca57f9d27c036f329a30c8f81b51c52bf BUG: 1492109 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: https://review.gluster.org/18306 Reviewed-by: Prashanth Pai <ppai> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Aravinda VK <avishwan> CentOS-regression: Gluster Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/