Re: [LTP] Container Test should not run on older distro kernel

[Garrett C. <yan...@gm...>]

On Mon, Feb 22, 2010 at 9:07 PM, Rishikesh K Rajak
<ris...@li...> wrote:
> Hi All,
>
> I ran feb'10 intermediate release on RHEL5.4. And found that it is
> running pidns testcase which is not at all require.
>
> Garret is it require to disable check_pidns_enabled.c which has been
> masked for now ? I think we will need this file as it does more than
> kernel version comparison.
>
> can someone look into it please ?
>
> Here are the failures which i am getting:
>
> =====================================================================
> ...
> COMMAND:    /opt/ltp/bin/ltp-pan  -e -S   -a 31429     -n 31429  -p  -f
> /tmp/ltp-wcBkk31437/alltests -l
> /opt/ltp/results/LTP_RUN_ON-2010_Feb_23-04h_51m_27s.log  -C
> /opt/ltp/output/LTP_RUN_ON-2010_Feb_23-04h_51m_27s.failed
> LOG File: /opt/ltp/results/LTP_RUN_ON-2010_Feb_23-04h_51m_27s.log
> FAILED COMMAND File:
> /opt/ltp/output/LTP_RUN_ON-2010_Feb_23-04h_51m_27s.failed
> Running tests.......
> <<<test_start>>>
> tag=Containers stime=1266918687
> cmdline="container_test.sh"
> contacts=""
> analysis=exit
> <<<test_output>>>
> incrementing stop
> /opt/ltp/testcases/bin/container_test.sh: line 13: check_for_unshare:
> command not found
> Uts namespaces not enabled in kernel.  Not running utsns tests.
> ipc namespaces not enabled in kernel.  Not running ipcns tests.
> Running pidns tests.
> pid_namespace1    0  TINFO  :  PIDNS test is running inside container
>
> pid_namespace1    1  TFAIL  :  FAIL: Got unexpected result of cpid=31542
> ppid=31541
>
> pid_namespace2    0  TINFO  :  Checking session id & group id inside
> container
>
> pid_namespace2    1  TFAIL  :  Got unexpected result ofGroup ID = 31544
> & Session ID = 31544
>
> pid_namespace3    0  TINFO  :   Checking pid for parent ns and
> container-init
>                Parent namespace pid = 31545,container parent pid =
> 31545,and container pid = 31546
> pid_namespace3    1  TFAIL  :  mount failed :
>
> pid_namespace3    2  TPASS  :  Got the proc file directory created by
> parent ns 31545
> pid_namespace4    1  TFAIL  :  got unexpected result of cpid=31548
> ppid=31547
> pid_namespace4    1  TFAIL  :  Container init is killed by SIGKILL !!!
> pidns05     1  TFAIL  :  FAIL: Got unexpected result of cpid=31551
> ppid=31550
>
> pidns05     1  TFAIL  :  Unable to create 5 containers
>
> pidns06     0  TINFO  :  Parent: Passing the pid of the process 31552
> pidns06     1  TFAIL  :  Unexpected result for Container:  init
> pid=31553 parent pid=31552
>
> pidns30     1  TBROK  :  parent: mq_open() failed (Permission denied)
> pidns31     1  TBROK  :  parent: mq_open() failed (Permission denied)
> pidns10     1  TBROK  :  cinit: pidns is not created.
> pidns10     1  TBROK  :  parent: container was terminated by Unknown
> signal 0
> pidns12     0  TINFO  :  parent: PID is 31558
> pidns12     1  TBROK  :  cinit: pidns is not created.
> pidns12     1  TBROK  :  parent: container did not respond!
> pidns13     1  TBROK  :  cinit1: pidns is not created.
> pidns13     1  TBROK  :  cinit2: pidns is not created.
> pidns16     1  TBROK  :  pidns is not created.
> pidns16     0  TINFO  :  sig_handler is signalled from pid  31563
> pidns16     0  TINFO  :  Container: Resumed after receiving SIGUSR1 from
> parentNS
> pidns16     2  TBROK  :  Unexpected value for Sending-ProcessID when
> signal handler called 31564
>
> pidns16     0  TINFO  :  Container: Resumed after sending SIGUSR1 from
> container itself
> pidns16     1  TPASS  :  container init continued successfuly, after
> handling signal -USR1
>
> pidns17     1  TBROK  :  cinit: pidns is not created.
>
> <----- stuck here, i never get the shell back here :(.
> ============================================================

    Well, it shouldn't be run on any kernels without container support
properly enabled, not just old kernels. I readded it from an old copy
in CVS.
Thanks,
-Garrett