Description of problem: delete-node not implemented Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
patches previously submitted (erroneously) under BZ 1188184
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#4) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#5) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#6) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#7) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#8) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#9) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#10) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#11) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10234 (common-ha: delete-node implementation) posted (#12) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/10234 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit d28a99d6f20650e5d78accb1e16bd3721a2b6d02 Author: Kaleb S. KEITHLEY <kkeithle> Date: Tue Apr 14 08:17:10 2015 -0400 common-ha: delete-node implementation omnibus patch consisting of: + completed implemenation of delete-node (BZ 1212823) + teardown leaves /var/lib/nfs symlink (BZ 1210712) + setup copy config, teardown clean /etc/cluster (BZ 1212823) setup for copy config, teardown clean /etc/cluster: 1. on one (primary) node in the cluster, run: `ssh-keygen -f /var/lib/glusterd/nfs/secret.pem` Press Enter twice to avoid passphrase. 2. deploy the pubkey ~root/.ssh/authorized keys on _all_ nodes, run: `ssh-copy-id -i /var/lib/glusterd/nfs/secret.pem.pub root@$node` 3. copy the keys to _all_ nodes in the cluster, run: `scp /var/lib/glusterd/nfs/secret.* $node:/var/lib/glusterd/nfs/` N.B. this allows setup, teardown, etc., to be run on any node Change-Id: I9fcd3a57073ead24cd2d0ef0ee7a67c524f3d4b0 BUG: 1213933 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/10234 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: soumya k <skoduri> Tested-by: Gluster Build System <jenkins.com>
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 [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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user