From 38ae8db3a107f5bcb4ffc5947cf590eb797f1ffd Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Thu, 20 Oct 2016 17:11:38 +0200 Subject: [PATCH] pmxcfs: fix wrong information now covered in pvecm The "Remove Cluster configuration" section is outdated and has also missing steps (e.g. stopping corosync before removing its config) We have the information in the pvecm.adoc (Cluster Manager) so delete the howto and reference the one from pvecm instead. Signed-off-by: Thomas Lamprecht --- pmxcfs.adoc | 31 +++---------------------------- pvecm.adoc | 1 + 2 files changed, 4 insertions(+), 28 deletions(-) diff --git a/pmxcfs.adoc b/pmxcfs.adoc index d35c960..764cdf4 100644 --- a/pmxcfs.adoc +++ b/pmxcfs.adoc @@ -174,34 +174,9 @@ The recommended way is to reinstall the node after you removed it from your cluster. This makes sure that all secret cluster/ssh keys and any shared configuration data is destroyed. -In some cases, you might prefer to put a node back to local mode -without reinstall, which is described here: - -* stop the cluster file system in `/etc/pve/` - - # systemctl stop pve-cluster - -* start it again but forcing local mode - - # pmxcfs -l - -* remove the cluster configuration - - # rm /etc/pve/cluster.conf - # rm /etc/cluster/cluster.conf - # rm /var/lib/pve-cluster/corosync.authkey - -* stop the cluster file system again - - # systemctl stop pve-cluster - -* restart PVE services (or reboot) - - # systemctl start pve-cluster - # systemctl restart pvedaemon - # systemctl restart pveproxy - # systemctl restart pvestatd - +In some cases, you might prefer to put a node back to local mode without +reinstall, which is described in +<> ifdef::manvolnum[] include::pve-copyright.adoc[] diff --git a/pvecm.adoc b/pvecm.adoc index 8b3290f..99fe3a9 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -295,6 +295,7 @@ cluster again, you have to * then join it, as explained in the previous section. +[[pvecm_separate_node_without_reinstall]] Separate A Node Without Reinstalling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~