Red Hat Bugzilla – Bug 1313628
Brick ports get changed after GlusterD restart
Last modified: 2016-06-16 09:59:06 EDT
The following sequence of steps can lead to the brick ports changing, which can break firewall rules and lead to a brick being inaccessible from the client.
1. Stop the volume
2. Stop glusterd on one node.
3a. Start the volume from some other node, or
3b. do a volume set operation
4. Start glusterd on the downed node again.
5. If 3b was done, start volume now.
Result: Brick ports on the downed node change
REVIEW: http://review.gluster.org/13578 (glusterd: Always copy old brick ports when importing) posted (#1) for review on master by Kaushal M (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/13578 (glusterd: Always copy old brick ports when importing) posted (#2) for review on master by Kaushal M (email@example.com)
COMMIT: http://review.gluster.org/13578 committed in master by Atin Mukherjee (firstname.lastname@example.org)
Author: Kaushal M <email@example.com>
Date: Wed Mar 2 15:19:30 2016 +0530
glusterd: Always copy old brick ports when importing
When an updated volinfo is imported in, the brick ports from the old
volinfo should be always copied.
Earlier, this was being done only if the old volinfo was stopped and
new volinfo was started. This could lead to brick ports chaging when the
following sequence of steps happened.
- A volume is stopped
- GlusterD is stopped on a peer
- The stopped volume is started
- The stopped GlusterD is started
This sequence would lead to bricks on the peer with re-started GlusterD
to get new ports, which could break firewall rules and could prevent
client access. This sequence could be hit when enabling management
encryption in a Gluster trusted storage pool.
Signed-off-by: Kaushal M <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Raghavendra Talur <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
Tested-by: Atin Mukherjee <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.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.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.