From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92428C433F5 for ; Fri, 21 Jan 2022 06:30:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348634AbiAUGaU (ORCPT ); Fri, 21 Jan 2022 01:30:20 -0500 Received: from smtp-out1.suse.de ([195.135.220.28]:53944 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233954AbiAUGaU (ORCPT ); Fri, 21 Jan 2022 01:30:20 -0500 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 6B922210E2; Fri, 21 Jan 2022 06:30:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1642746619; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JACFRqlC966zZ1PtI0GVzYG9qWesDuNqnrbnJs9CP38=; b=n3m9VYgmShXbN86U6M59f+BWTs/pmCe+kyTVBJMekhfleqGSvbn+W3baa0KBRkCI4wTOXJ m/KVmYKjgQqXfeQE5vEDfbWgFGigye8IFhEFyNI4KJQ+kxKinW4OUNyku+yMUzeNn/vQmv Ha1OynsNBVNH8cZryV7k+nKzaEVFgqs= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1642746619; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JACFRqlC966zZ1PtI0GVzYG9qWesDuNqnrbnJs9CP38=; b=j5OYB2cI8+ULYThes0o7QMzfeRPmoWadHus4B7oM03TVZbTd7Rz5MQPUSTZDg1ywtipf+3 DaCl45bKOTLhBnBA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 3140B13345; Fri, 21 Jan 2022 06:30:19 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 9MB2CvtS6mEYCgAAMHmgww (envelope-from ); Fri, 21 Jan 2022 06:30:19 +0000 Date: Fri, 21 Jan 2022 07:30:17 +0100 From: Petr Vorel To: Nikita Yushchenko Cc: ltp@lists.linux.it, kernel@openvz.org, linux-nfs@vger.kernel.org, Steve Dickson , NeilBrown Subject: Re: [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation Message-ID: Reply-To: Petr Vorel References: <20220120143727.27057-1-nikita.yushchenko@virtuozzo.com> <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org > > > I had to add this patch to make 'runltp -f net.rpc' pass just after > > > container is started - that happens in container autotests here. > > Yep, I suspected this. Because on normal linux distro it's working right after > > boot (tested on rpc01.sh). Can't this be a setup issue? > This depends on what is installed and how it is configured. > But definitely the state with rpcbind process not running and systemd is > listening on rpcbind sockets - is valid. > In the setup where the issue was caught, the test harness creates a > container with minimal centos8 setup inside, boots it, and starts ltp > inside. > Just reproduced manually: > [root@vz8 ~]# vzctl start 1000 > Starting Container ... > ... > [root@vz8 ~]# vzctl enter 1000 > entered into CT 1000 > CT-1000 /# pidof rpcbind > CT-1000 /# rpcinfo > /dev/null 2>&1 > CT-1000 /# pidof rpcbind > 678 > CT-1000 /# Thanks for info. I'm asking because if it's a setup bug it should not be hidden by workaround but reported. I suppose normal Centos8 VM works. Kind regards, Petr From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B72E4C433F5 for ; Fri, 21 Jan 2022 06:30:32 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id A54DB3C96D8 for ; Fri, 21 Jan 2022 07:30:30 +0100 (CET) Received: from in-7.smtp.seeweb.it (in-7.smtp.seeweb.it [IPv6:2001:4b78:1:20::7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id 615053C8DB2 for ; Fri, 21 Jan 2022 07:30:20 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-7.smtp.seeweb.it (Postfix) with ESMTPS id 6CDA52000A0 for ; Fri, 21 Jan 2022 07:30:19 +0100 (CET) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 6B922210E2; Fri, 21 Jan 2022 06:30:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1642746619; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JACFRqlC966zZ1PtI0GVzYG9qWesDuNqnrbnJs9CP38=; b=n3m9VYgmShXbN86U6M59f+BWTs/pmCe+kyTVBJMekhfleqGSvbn+W3baa0KBRkCI4wTOXJ m/KVmYKjgQqXfeQE5vEDfbWgFGigye8IFhEFyNI4KJQ+kxKinW4OUNyku+yMUzeNn/vQmv Ha1OynsNBVNH8cZryV7k+nKzaEVFgqs= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1642746619; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=JACFRqlC966zZ1PtI0GVzYG9qWesDuNqnrbnJs9CP38=; b=j5OYB2cI8+ULYThes0o7QMzfeRPmoWadHus4B7oM03TVZbTd7Rz5MQPUSTZDg1ywtipf+3 DaCl45bKOTLhBnBA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 3140B13345; Fri, 21 Jan 2022 06:30:19 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 9MB2CvtS6mEYCgAAMHmgww (envelope-from ); Fri, 21 Jan 2022 06:30:19 +0000 Date: Fri, 21 Jan 2022 07:30:17 +0100 From: Petr Vorel To: Nikita Yushchenko Message-ID: References: <20220120143727.27057-1-nikita.yushchenko@virtuozzo.com> <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> X-Virus-Scanned: clamav-milter 0.102.4 at in-7.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Petr Vorel Cc: NeilBrown , linux-nfs@vger.kernel.org, kernel@openvz.org, Steve Dickson , ltp@lists.linux.it Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" > > > I had to add this patch to make 'runltp -f net.rpc' pass just after > > > container is started - that happens in container autotests here. > > Yep, I suspected this. Because on normal linux distro it's working right after > > boot (tested on rpc01.sh). Can't this be a setup issue? > This depends on what is installed and how it is configured. > But definitely the state with rpcbind process not running and systemd is > listening on rpcbind sockets - is valid. > In the setup where the issue was caught, the test harness creates a > container with minimal centos8 setup inside, boots it, and starts ltp > inside. > Just reproduced manually: > [root@vz8 ~]# vzctl start 1000 > Starting Container ... > ... > [root@vz8 ~]# vzctl enter 1000 > entered into CT 1000 > CT-1000 /# pidof rpcbind > CT-1000 /# rpcinfo > /dev/null 2>&1 > CT-1000 /# pidof rpcbind > 678 > CT-1000 /# Thanks for info. I'm asking because if it's a setup bug it should not be hidden by workaround but reported. I suppose normal Centos8 VM works. Kind regards, Petr -- Mailing list info: https://lists.linux.it/listinfo/ltp