public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage] nfs: check connection: support NFSv4-only servers without rpcbind
Date: Mon, 23 Jan 2023 10:14:50 +0100	[thread overview]
Message-ID: <20230123091450.58359-1-f.ebner@proxmox.com> (raw)

by simply doing a ping with the expected port as a fallback when the
rpcinfo command fails.

The timeout was chosen to be 2 seconds, because that's what the
existing callers of tcp_ping() in the iSCSI and GlusterFS plugins use.

Alternatively, the existing check could be replaced, but that would
1. Dumb down the check.
2. Risk breakage in some corner case that's yet to be discovered.
3. It would still be necessary to use rpcinfo (or dumb the check down
even further) in case port=0; from 'man 5 nfs' about the NFSv4 'port'
option:
> If the specified port value is 0, then the NFS client uses the NFS
> service port number advertised by the server's rpcbind service.

Reported in the community forum:
https://forum.proxmox.com/threads/118466/post-524449
https://forum.proxmox.com/threads/120774/

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 PVE/Storage/NFSPlugin.pm | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/PVE/Storage/NFSPlugin.pm b/PVE/Storage/NFSPlugin.pm
index 0bdde84..c2d4176 100644
--- a/PVE/Storage/NFSPlugin.pm
+++ b/PVE/Storage/NFSPlugin.pm
@@ -168,7 +168,9 @@ sub check_connection {
     my $opts = $scfg->{options};
 
     my $cmd;
-    if (defined($opts) && $opts =~ /vers=4.*/) {
+
+    my $is_v4 = defined($opts) && $opts =~ /vers=4.*/;
+    if ($is_v4) {
 	my $ip = PVE::JSONSchema::pve_verify_ip($server, 1);
 	if (!defined($ip)) {
 	    $ip = PVE::Network::get_ip_from_hostname($server);
@@ -185,6 +187,16 @@ sub check_connection {
 
     eval { run_command($cmd, timeout => 10, outfunc => sub {}, errfunc => sub {}) };
     if (my $err = $@) {
+	if ($is_v4) {
+	    my $port = 2049;
+	    $port = $1 if defined($opts) && $opts =~ /port=(\d+)/;
+
+	    # rpcinfo is expected to work when the port is 0 (see 'man 5 nfs') and tcp_ping()
+	    # defaults to port 7 when passing in 0.
+	    return 0 if $port == 0;
+
+	    return PVE::Network::tcp_ping($server, $port, 2);
+	}
 	return 0;
     }
 
-- 
2.30.2





             reply	other threads:[~2023-01-23  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  9:14 Fiona Ebner [this message]
2023-01-24 16:18 ` [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=20230123091450.58359-1-f.ebner@proxmox.com \
    --to=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal