All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Yushchenko <nikita.yushchenko@virtuozzo.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, kernel@openvz.org, linux-nfs@vger.kernel.org,
	Steve Dickson <SteveD@redhat.com>, NeilBrown <neilb@suse.de>
Subject: Re: [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation
Date: Fri, 21 Jan 2022 08:41:47 +0300	[thread overview]
Message-ID: <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> (raw)
In-Reply-To: <YepE066MwWSf7wAK@pevik>

> 
>> 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 /#

WARNING: multiple messages have this Message-ID (diff)
From: Nikita Yushchenko via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: NeilBrown <neilb@suse.de>,
	linux-nfs@vger.kernel.org, kernel@openvz.org,
	Steve Dickson <SteveD@redhat.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation
Date: Fri, 21 Jan 2022 08:41:47 +0300	[thread overview]
Message-ID: <31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com> (raw)
In-Reply-To: <YepE066MwWSf7wAK@pevik>

> 
>> 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 /#

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-01-21  5:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 14:37 [LTP] [PATCH] rpc_lib.sh: fix portmapper detection in case of socket activation Nikita Yushchenko via ltp
2022-01-20 21:01 ` Petr Vorel
2022-01-20 21:01   ` [LTP] " Petr Vorel
2022-01-21  4:57   ` Nikita Yushchenko
2022-01-21  4:57     ` [LTP] " Nikita Yushchenko via ltp
2022-01-21  5:29     ` Petr Vorel
2022-01-21  5:29       ` [LTP] " Petr Vorel
2022-01-21  5:41       ` Nikita Yushchenko [this message]
2022-01-21  5:41         ` Nikita Yushchenko via ltp
2022-01-21  6:30         ` Petr Vorel
2022-01-21  6:30           ` [LTP] " Petr Vorel
2022-01-21  6:50           ` Nikita Yushchenko
2022-01-21  6:50             ` [LTP] " Nikita Yushchenko via ltp
2022-01-21 20:44   ` NeilBrown
2022-01-21 20:44     ` [LTP] " NeilBrown
2022-01-24  6:09     ` Petr Vorel
2022-01-24  6:09       ` [LTP] " Petr Vorel
2022-01-24 21:11 ` Petr Vorel

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=31a29913-11f4-8dfd-6c5c-735673dcd1a2@virtuozzo.com \
    --to=nikita.yushchenko@virtuozzo.com \
    --cc=SteveD@redhat.com \
    --cc=kernel@openvz.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=neilb@suse.de \
    --cc=pvorel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.