[Bugs] [Bug 1313628] New: Brick ports get changed after GlusterD restart
bugzilla at redhat.com
bugzilla at redhat.com
Wed Mar 2 06:11:30 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1313628
Bug ID: 1313628
Summary: Brick ports get changed after GlusterD restart
Product: GlusterFS
Version: mainline
Component: glusterd
Assignee: kaushal at redhat.com
Reporter: kaushal at redhat.com
CC: bugs at gluster.org
Blocks: 1306656
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
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1306656
[Bug 1306656] [GSS] - Brick ports changed after configuring I/O and
management encryption
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qvVSjFvzEr&a=cc_unsubscribe
More information about the Bugs
mailing list