From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH cluster] pvecm add: require user to navigate out of /etc/pve
Date: Sat, 11 Mar 2023 18:01:17 +0100 [thread overview]
Message-ID: <60ff5428-fa59-c253-0ac2-38cfaa4dbdde@proxmox.com> (raw)
In-Reply-To: <20230309123019.1080105-1-f.weber@proxmox.com>
Am 09/03/2023 um 13:30 schrieb Friedrich Weber:
> If `pvecm add` is issued from /etc/pve (or any subdirectory), it
> prints some errors:
>
> [...]
> shell-init: error retrieving current directory: getcwd: cannot
> access parent directories: Transport endpoint is not connected
> [...]
> successfully added node 'pve-c2' to cluster.
> cannot fetch initial working directory: Transport endpoint is not
> connected at /usr/share/perl5/PVE/CLI/pvecm.pm line 446.
>
> The reason is that `pvecm add` restarts pmxcfs, which re-mounts the
> fuse mount at /etc/pve, invalidating pvecm's working directory.
>
> The error messages give the impression that something went wrong.
> Indeed, the second error indicates the temporary directory is not
> cleaned up. The cluster join itself actually works, though.
>
> The issue could be fixed by chdir'ing to / in `pvecm add`. However,
> the user's shell would still remain in the now-invalid /etc/pve,
> potentially leading to confusing "transport endpoint not connected"
> messages in future interactions.
>
> To avoid this, require the user to chdir out of /etc/pve before
> running `pvecm add`.
>
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> data/PVE/CLI/pvecm.pm | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2023-03-11 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:30 [pve-devel] " Friedrich Weber
2023-03-11 17:01 ` Thomas Lamprecht [this message]
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=60ff5428-fa59-c253-0ac2-38cfaa4dbdde@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-devel@lists.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