Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 21 May 2021 14:39:39 -0400
From:   "J. Bruce Fields" <bfields@redhat.com>
To:     Petr Vorel <pvorel@suse.cz>
Cc:     linux-nfs@vger.kernel.org, Yong Sun <yosun@suse.com>
Subject: Re: pynfs: COUR2, EID50 test failures
Message-ID: <YKf+a7e4lv2BwBBQ@pick.fieldses.org>
References: <YKdXZa6Izs7kqgfE@pevik>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YKdXZa6Izs7kqgfE@pevik>
Precedence: bulk

On Fri, May 21, 2021 at 08:47:01AM +0200, Petr Vorel wrote:
> Hi Bruce,
> 
> what's wrong with pynfs COUR2, EID50 tests?
> They're failing on various kernels.
> I got these failures on 5.11.12 (openSUSE package), 5.13.0-rc2 (mainline on
> openSUSE), 4.9.0 (Debian package):
> 
> COUR2    st_courtesy.testLockSleepLock                            : FAILURE
>            OP_OPEN should return NFS4_OK, instead got
>            NFS4ERR_GRACE

Are you running it immediately after starting the server?  If so, that's
expected.  Personally my test scripts mount the server and create a file
there before running pynfs tests.  The create won't return until the
grace period's done.

Might be worth documenting in the README, or teaching pynfs to wait
before running tests.

> EID50    st_exchange_id.testSSV                                   : FAILURE
>            nfs4lib.NFS4Error: OP_EXCHANGE_ID should return
>            NFS4_OK, instead got NFS4ERR_ENCR_ALG_UNSUPP
> 
> Nothing in dmesg (tested with "rpcdebug -m nfsd -s lockd").
> Or is it just my wrong setup?

SSV support is optional.  We should probably drop the "all" tag from
that test.

--b.