public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm
Date: Thu, 23 Jul 2020 09:17:11 +0200	[thread overview]
Message-ID: <20200723071711.GA5243@mala.proxmox.com> (raw)
In-Reply-To: <94ed3288-870c-af50-f4a6-c0b03b1b30e8@proxmox.com>

On Wed, Jul 22, 2020 at 12:31:53PM +0200, Thomas Lamprecht wrote:
> On 22.07.20 12:20, Dominic Jäger wrote:
> > /etc/corosync/* includes the directory uidgid.d.
> > Consequentlly, a correct rm call requires -r.
> 
> Does leaving this directory left-over causes any issues?
When I tested this it was empty. It should contain some optional permissions
for corosync [0].

We later say "(...) delete all remaining files left from the old cluster. This
ensures that the node can be added to another cluster again without problems."

Couldn't those permissions then be active in a potential new cluster?

> IIRC, I omit the "-r" explicitly as there can be also a directory from
> a qdevice or other ones, which we do not want to remove - to level
> corosync/* files where all desired to be removed, thus this rm varian.

Looking at the quote from before, why do we want some connection to the qdevice
to remain?

> But, maybe we should rather change it to:
> # rm -f /etc/corosync/corosync.conf /etc/corosync/authkey

I just tried it without -f:

root@pveA:/etc/corosync# ls
authkey  corosync.conf  uidgid.d
root@pveA:/etc/corosync# rm /etc/corosync/corosync.conf /etc/corosync/authkey
root@pveA:/etc/corosync# ls
uidgid.d

And the node was removed from the cluster as expected.

I can test it with permissions and qdevice, too. Would just have look up how
that actually works.

[0] https://www.mankier.com/8/pcs (ctrl+f for uidgid)




  reply	other threads:[~2020-07-23  7:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 10:20 Dominic Jäger
2020-07-22 10:20 ` [pve-devel] [PATCH docs 2/2] pvecm: Add output for delnode Dominic Jäger
2020-08-20 13:31   ` [pve-devel] applied: " Thomas Lamprecht
2020-07-22 10:31 ` [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm Thomas Lamprecht
2020-07-23  7:17   ` Dominic Jäger [this message]
2020-08-20 13:31 ` [pve-devel] applied: " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200723071711.GA5243@mala.proxmox.com \
    --to=d.jaeger@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal