Bug 1408110
| Summary: | [GANESHA] Adding node to ganesha cluster is not assigning the correct VIP to the new node | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Soumya Koduri <skoduri> |
| Component: | common-ha | Assignee: | Soumya Koduri <skoduri> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.9 | CC: | bugs, kkeithle, msaini, rhs-bugs, storage-qa-internal |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1406410 | Environment: | |
| Last Closed: | 2017-03-08 10:23:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1406410 | ||
| Bug Blocks: | 1406401 | ||
|
Description
Soumya Koduri
2016-12-22 07:21:04 UTC
REVIEW: http://review.gluster.org/16269 (common-ha: Correct the VIP assigned to the new node added) posted (#1) for review on release-3.9 by soumya k (skoduri) REVIEW: http://review.gluster.org/16269 (common-ha: Correct the VIP assigned to the new node added) posted (#2) for review on release-3.9 by soumya k (skoduri) COMMIT: http://review.gluster.org/16269 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) ------ commit 5a65416b14da7b06aff9319f39c5c4f4e7c884fb Author: Soumya Koduri <skoduri> Date: Tue Dec 20 18:22:02 2016 +0530 common-ha: Correct the VIP assigned to the new node added There is a regression introduced with patch#16115. An incorrect VIP gets assigned to the new node being added to the cluster. This patch fixes the same. This is backport of below mainline patch: http://review.gluster.org/16213 > Change-Id: I468c7d16bf7e4efa04692db83b1c5ee58fbb7d5f > BUG: 1406410 > Signed-off-by: Soumya Koduri <skoduri> Change-Id: Iccac83720280d823b36c1e47194b2e17226c91db BUG: 1408110 Signed-off-by: Soumya Koduri <skoduri> Reviewed-on: http://review.gluster.org/16269 Reviewed-by: jiffin tony Thottan <jthottan> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kaleb KEITHLEY <kkeithle> NetBSD-regression: NetBSD Build System <jenkins.org> 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.9.1, please open a new bug report. glusterfs-3.9.1 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/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |