From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs41client: fix raising an error when pnfs test hits non pnfs server
Date: Wed, 22 Jul 2020 09:58:39 -0400 [thread overview]
Message-ID: <20200722135839.GA28219@fieldses.org> (raw)
In-Reply-To: <20200721194358.18132-1-tigran.mkrtchyan@desy.de>
On Tue, Jul 21, 2020 at 09:43:58PM +0200, Tigran Mkrtchyan wrote:
> fail function is not defined
It's used elsewhere, e.g. st_sequence.py, I think we just need an
import.
>
> Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
> ---
> nfs4.1/nfs4client.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/nfs4.1/nfs4client.py b/nfs4.1/nfs4client.py
> index f06d9c5..3d55f96 100644
> --- a/nfs4.1/nfs4client.py
> +++ b/nfs4.1/nfs4client.py
> @@ -1,7 +1,7 @@
> import use_local # HACK so don't have to rebuild constantly
> import rpc.rpc as rpc
> import nfs4lib
> -from nfs4lib import NFS4Error, NFS4Replay, inc_u32
> +from nfs4lib import NFS4Error, NFS4Replay, inc_u32, UnexpectedCompoundRes
> from xdrdef.nfs4_type import *
> from xdrdef.nfs4_const import *
> from xdrdef.sctrl_pack import SCTRLPacker, SCTRLUnpacker
> @@ -331,7 +331,7 @@ class NFS4Client(rpc.Client, rpc.Server):
> # Make sure E_ID returns MDS capabilities
> c = self.new_client(name, flags=flags)
> if not c.flags & EXCHGID4_FLAG_USE_PNFS_MDS:
> - fail("Server can not be used as pnfs metadata server")
> + raise UnexpectedCompoundRes("Server can not be used as pnfs metadata server")
> s = c.create_session(sec=sec)
> s.compound([op4.reclaim_complete(FALSE)])
> return s
> --
> 2.26.2
prev parent reply other threads:[~2020-07-22 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 19:43 [PATCH] nfs41client: fix raising an error when pnfs test hits non pnfs server Tigran Mkrtchyan
2020-07-22 13:58 ` J. Bruce Fields [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=20200722135839.GA28219@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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