[pve-devel] applied: [PATCH v2] pmxcfs: fix wrong information now covered in pvecm

Thomas Lamprecht t.lamprecht at proxmox.com
Fri Oct 21 08:41:39 CEST 2016


On 10/20/2016 05:34 PM, Dietmar Maurer wrote:
> applied, but see comment inline:
>
>> On October 20, 2016 at 5:11 PM Thomas Lamprecht <t.lamprecht at proxmox.com>
>> wrote:
>>
>>
>> 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 <t.lamprecht at proxmox.com>
>> ---
>>
>> changes sinve v1:
>> * add reference and link it instead of defines (defer from wrapping
>>    a link into multiple lines for now)
>>
>>   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
> IMHO it is important to remove the secret corosync.authkey. But this
> is missing in the new docs. Please can you add that again?

The information is still there, this was also outdated information. In PVE
4.x with corosync  2.x the authkey is not saved in the
/var/lib/pve-cluster/corosync.authkey directory but in /etc/corosync/authkey
and this gets handled by:

  > rm /etc/corosync/*

in the new docs.






More information about the pve-devel mailing list