Bug 1450055 - [GANESHA] Adding a node to existing cluster failed to start pacemaker service on new node
Summary: [GANESHA] Adding a node to existing cluster failed to start pacemaker service...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: common-ha
Version: 3.8
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On: glusterfs-3.8.13 1450053
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-11 13:00 UTC by Kaleb KEITHLEY
Modified: 2017-06-29 09:54 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8.13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1450053
Environment:
Last Closed: 2017-06-29 09:54:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2017-05-11 13:28:44 UTC
REVIEW: https://review.gluster.org/17256 (common-ha: adding a node to existing cluster failed to start pacemaker) posted (#1) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2017-05-24 00:17:06 UTC
COMMIT: https://review.gluster.org/17256 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) 
------
commit 6c4255c701160d10f71c9be11983f309086165c7
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Thu May 11 09:25:05 2017 -0400

    common-ha: adding a node to existing cluster failed to start pacemaker
    
    selected fixes back-ported from release-3.10
    
    Change-Id: I44876305630a82e471824c085ed9ac58df08caa2
    BUG: 1450055
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: https://review.gluster.org/17256
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Niels de Vos 2017-06-29 09:54:50 UTC
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.13, please open a new bug report.

glusterfs-3.8.13 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] https://lists.gluster.org/pipermail/announce/2017-June/000075.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.