Difference between revisions of "EMI gLExec release test plan and report"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 247: Line 247:
  
 
The SCAS-client plugin will not trigger a segmentation fault and pull gLExec with it when the SCAS host is not a FQDN.
 
The SCAS-client plugin will not trigger a segmentation fault and pull gLExec with it when the SCAS host is not a FQDN.
 +
 +
==== Savannah: https://savannah.cern.ch/bugs/?64057 ====
 +
DESCRIPTION: glexec fails with a misleading error message if the configuration cannot be read
 +
 +
REPRODUCE: install glexec in setuid mode (-r-sr-sr-s root.glexec) and the config file as (-r--r----- root.root)
 +
 +
CHECK: Error message
 +
 +
 +
 +
PASSED: [gLExec]:  User tester (uid=502) is not whitelisted, i.e. may not invoke gLExec.
 +
If this is unexpected, ask the sysadmin to check the syslog and the
 +
permissions of the config file.
 +
 +
==== Savannah: https://savannah.cern.ch/bugs/?77767 ====
 +
DESCRIPTION: yaim-glexec-wn must put GLEXEC_LOCATION in grid-env.sh
 +
 +
REPRODUCE: install YAIM, run yaim-glexec-wn
 +
 +
CHECK: content of grid-env.sh
 +
 +
FAILED: No GLEXEC_LOCATION exported in the shell
 +
 +
PASSED: GLEXEC_LOCATION available and set
 +
 +
 +
==== Savannah: https://savannah.cern.ch/bugs/?82714 ====
 +
DESCRIPTION: YAIM should not configure LCAS when Argus is used
 +
 +
REPRODUCE:
 +
install and configure yaim-glexec-wn
 +
configure site-info.def to use ARGUS: set
 +
GLEXEC_WN_ARGUS_ENABLED=yes
 +
in siteinfo/services/glite-glexec_wn
 +
run YAIM
 +
CHECK: contents of /etc/glexec.conf
 +
 +
FAILED: configuration file contains use_lcas = yes
 +
 +
PASSED: configuration file must contain use_lcas = no (default is to use LCAS). (this test passed; where do I record this?)
 +
 +
==== Savannah: https://savannah.cern.ch/bugs/?86453 ====
 +
DESCRIPTION: Permissions on glexec in RPM are not setuid root
 +
 +
REPRODUCE: rpm -qvl glexec
 +
 +
CHECK: permission of /usr/sbin/glexec
 +
 +
FAILED:
 +
---x--x--x 1 root root      147456 Apr  3 02:59 /usr/sbin/glexec
 +
PASSED:
 +
---s--x--x 1 root root      147456 Apr  3 02:59 /usr/sbin/glexec
 +
 +
https://savannah.cern.ch/bugs/?88318
 +
LCMAPS excessive logging (2)
 +
REPRODUCE: Normal installation with LCMAPS =<1.4.x, log with gLExec to Syslog, configure to log LOG_INFO
 +
CHECK: Amount of log lines
 +
FAILED: More then O(10) log lines
 +
 +
 +
https://savannah.cern.ch/bugs/?89773
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=1474
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=1475
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=1476
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=1641
 +
Mirror bug for gLExec
 +
 +
https://savannah.cern.ch/bugs/?89792
 +
YAIM-gLExec-wn should let gLExec do the userswitch
 +
REPRODUCE: Run YAIM to observe the configuration in the glexec.conf and lcmaps.db
 +
 +
 +
PASSED: On successful switch by glexec
 +
 +
https://savannah.cern.ch/bugs/?91835
 +
https://savannah.cern.ch/bugs/index.php?72377
 +
https://savannah.cern.ch/bugs/index.php?72378
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=465
 +
https://rt.egi.eu/rt/Ticket/Display.html?id=466
 +
Mirror bug for gLExec
 +
 +
https://savannah.cern.ch/bugs/?91836
 +
Signal handling in gLExec 0.9.0 can hang up gLExec
 +
REPRODUCE: run glexec and flood it with signals after a very small delay, such that it traps signals e.g. during a syslog call. E.g. run several times:
 +
#!/bin/bash
 +
export GLEXEC_CLIENT_CERT=/tmp/x509up_u`id -u`
 +
export X509_USER_PROXY=/tmp/x509up_u`id -u`
 +
/usr/sbin/glexec /usr/bin/id -a &
 +
pid=$!
 +
ps -fp $pid
 +
for ((i=1; i<100; i++));do
 +
s=$((i%64+1))
 +
((s==9 || s==19 || s==32 || s==33)) && s=11
 +
kill -$s $pid
 +
done
 +
CHECK: gLExec does not hang up, even after many times.
 +
FAIL: gLExec locks up and can only be killed with a kill -9, an strace will show gLExec hangs is a lock.
 +
PASSED: gLExec will get interrupted or killed in a clean way.
 +
 +
https://savannah.cern.ch/bugs/?91963
 +
gLExec should check whether stdin/stdout/stderr exists
 +
REPRODUCE: run in non-setuid mode:
 +
/usr/sbin/glexec /bin/sleep 60 1>&- 2>&- 0<&-
 +
CHECK: run:
 +
ls -l /proc/`ps -o pid= -C glexec`/fd/[012]
 +
FAILED: e.g. filedescriptor 2 is missing, and filedescriptors 0 and 1 point to a socket (from syslog)
 +
PASSED: filedescriptors 0-2 point to /dev/null
 +
 +
https://savannah.cern.ch/bugs/?92667
 +
gLExec 0.9.3 segfaults when preserve_env_variables is used in config
 +
REMARKS: Bug is cross-platform, but segfault occurs on SL6
 +
REPRODUCE: install glexec-0.9.3 on RH6 system and add preserve_env_variables = anything to the /etc/glexec.conf, then run /usr/sbin/glexec /usr/bin/id
 +
CHECK: with preserve_env_variables there should be no problem in running glexec
 +
FAILED: [gLExec]:  Premature exit due to signal, signal: 11
 +
PASSED: no error message
 +
 +
https://savannah.cern.ch/bugs/?92812
 +
LCMAPS without GSI SIGABORTs in StoRM EMI 2 RC3
 +
REPRODUCE: install lcmaps version 1.5.2 (EMI RC 3)
 +
CHECK: run llrun using the without GSI interface.
 +
PASSED: On successful llrun
 +
FAILED: On segmentation fault or abort based on an invalid free.
 +
REMARKS: The 1.5.3 version and newer of LCMAPS fixes the problem observed here
 +
 +
https://savannah.cern.ch/bugs/?92818
 +
glite_wms_wmproxy_server crashes with a SEGV when using the LCMAPS 1.5.2
 +
REPRODUCE: install lcmaps version 1.5.2 (EMI RC 3)
 +
CHECK: run llrun using the without GSI interface.
 +
PASSED: On successful llrun
 +
FAILED: On segmentation fault or abort based on an invalid free.
 +
REMARKS: The 1.5.3 version and newer of LCMAPS fixes the problem observed here
 +
REMARKS: Similar to Savannah bug 92812
 +
 +
https://savannah.cern.ch/bugs/?93187
 +
glexec-configure script contains some errors
 +
 +
https://savannah.cern.ch/bugs/?93190
 +
LCMAPS gives misleading error when PDL parsing fails
 +
 +
CHECK: Error message from LCMAPS
 +
PASSED: Error message flags it as a parse error
 +
FAILED: Error message flags it as an out of memory error
 +
 +
https://savannah.cern.ch/bugs/?93248
 +
gLExec in non-linger mode does not set umask() correctly.
 +
REPRODUCE: Install glexec version 0.9.5 and disable linger mode (linger=no)
 +
CHECK:
 +
umask 0123; /tmp/dummy/usr/sbin/glexec /bin/bash -c umask
 +
PASSED: output should be 0123
 +
FAILED: output is 0077 (internal umask setting for glexec)

Revision as of 15:10, 14 May 2012

Retrieved from "https://wiki.nikhef.nl/grid/index.php?title=EMI_gLExec_release_test_plan_and_report&oldid=7914"