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

From PDP/Grid Wiki
Jump to navigationJump to search
 
(10 intermediate revisions by the same user not shown)
Line 247: Line 247:
 
DESCRIPTION: glexec fails with a misleading error message if the configuration cannot be read
 
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)
+
REPRODUCE: install glexec in setuid mode
 +
-r-sr-sr-s root.glexec /usr/sbin/glexec
 +
and the config file as
 +
-r--r----- root.root   /etc/glexec.conf
  
 
CHECK: Error message
 
CHECK: Error message
  
−
FAILED: Get �[gLExec]:  The user, uid=502(tester), is not whitelisted. The calling user account is not privileged to execute and use gLExec.�
+
FAILED: Get
 +
[gLExec]:  The user, uid=502(tester), is not whitelisted. The calling user account is not privileged to execute and use gLExec.
  
−
PASSED: [gLExec]:  User tester (uid=502) is not whitelisted, i.e. may not invoke gLExec.
+
PASSED:  
−
If this is unexpected, ask the sysadmin to check the syslog and the
+
[gLExec]:  User tester (uid=502) is not whitelisted, i.e. may not invoke gLExec.
−
permissions of the config file.
+
          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 ====
 
==== Savannah: https://savannah.cern.ch/bugs/?77767 ====
Line 272: Line 277:
  
 
REPRODUCE:
 
REPRODUCE:
−
install and configure yaim-glexec-wn
+
* install and configure yaim-glexec-wn
−
configure site-info.def to use ARGUS: set
+
* configure site-info.def to use ARGUS: set in <tt>siteinfo/services/glite-glexec_wn</tt>
 
  GLEXEC_WN_ARGUS_ENABLED=yes
 
  GLEXEC_WN_ARGUS_ENABLED=yes
−
in siteinfo/services/glite-glexec_wn
+
* run YAIM
−
run YAIM
 
−
CHECK: contents of /etc/glexec.conf
 
  
−
FAILED: configuration file contains use_lcas = yes
+
CHECK: contents of <tt>/etc/glexec.conf</tt>
  
−
PASSED: configuration file must contain use_lcas = no (default is to use LCAS). (this test passed; where do I record this?)
+
FAILED: configuration file contains <tt>use_lcas = yes</tt>
 +
 
 +
PASSED: configuration file must contain <tt>use_lcas = no</tt> (default is to use LCAS).
  
 
==== Savannah: https://savannah.cern.ch/bugs/?86453 ====
 
==== Savannah: https://savannah.cern.ch/bugs/?86453 ====
Line 319: Line 324:
 
REPRODUCE: Run YAIM to observe the configuration in the glexec.conf and lcmaps.db
 
REPRODUCE: Run YAIM to observe the configuration in the glexec.conf and lcmaps.db
  
−
CHECK: Check if the posix_enf plugin is NOT configured in the lcmaps.db and that the glexec.conf has the configuration: user_identity_switch_by = {glexec,lcmaps} to use �glexec� as the �switch by� setting.
+
CHECK: Check if the posix_enf plugin is NOT configured in the lcmaps.db and that the glexec.conf has the configuration: user_identity_switch_by = {glexec,lcmaps} to use �glexec� as the �switch by� setting or has no setting at all (default is switch by glexec).
  
 
FAILED: If the configuration in the glexec.conf or lcmaps.db does not reflect a working �user_identity_switch_by = glexec� configuration
 
FAILED: If the configuration in the glexec.conf or lcmaps.db does not reflect a working �user_identity_switch_by = glexec� configuration
Line 337: Line 342:
  
 
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:
 
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
+
<pre>
−
export GLEXEC_CLIENT_CERT=/tmp/x509up_u`id -u`
+
#!/bin/bash
−
export X509_USER_PROXY=/tmp/x509up_u`id -u`
+
export GLEXEC_CLIENT_CERT=/tmp/x509up_u`id -u`
−
/usr/sbin/glexec /usr/bin/id -a &
+
export X509_USER_PROXY=/tmp/x509up_u`id -u`
−
pid=$!
+
/usr/sbin/glexec /usr/bin/id -a &
−
ps -fp $pid
+
pid=$!
−
for ((i=1; i<100; i++));do
+
ps -fp $pid
−
s=$((i%64+1))
+
for ((i=1; i<100; i++));do
−
((s==9 || s==19 || s==32 || s==33)) && s=11
+
      s=$((i%64+1))
−
kill -$s $pid
+
      ((s==9 || s==19 || s==32 || s==33)) && s=11
−
done
+
      kill -$s $pid
 +
done
 +
</pre>
  
 
CHECK: gLExec does not hang up, even after many times.
 
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.
+
FAIL: gLExec locks up and can only be killed with a kill -9, an strace will show gLExec hangs in a lock.
  
 
PASSED: gLExec will get interrupted or killed in a clean way.
 
PASSED: gLExec will get interrupted or killed in a clean way.
Line 377: Line 384:
 
CHECK: with preserve_env_variables there should be no problem in running glexec
 
CHECK: with preserve_env_variables there should be no problem in running glexec
  
−
FAILED: [gLExec]:  Premature exit due to signal, signal: 11
+
FAILED:
 +
[gLExec]:  Premature exit due to signal, signal: 11
  
−
PASSED: no error message
+
PASSED: no error message, normal execution.
  
 
==== Savannah: https://savannah.cern.ch/bugs/?92812 ====
 
==== Savannah: https://savannah.cern.ch/bugs/?92812 ====
Line 411: Line 419:
 
==== Savannah: https://savannah.cern.ch/bugs/?93187 ====
 
==== Savannah: https://savannah.cern.ch/bugs/?93187 ====
 
DESCRIPTION: glexec-configure script contains some errors
 
DESCRIPTION: glexec-configure script contains some errors
 +
 +
REPRODUCE: run
 +
/usr/sbin/glexec-configure -o /tmp/glexec.conf -d /tmp/lcmaps.db argus argus.testbed
 +
 +
CHECK: the contents of /tmp/glexec.conf and /tmp/lcmaps.db
 +
 +
FAIL: e.g. endpoint line in pepc entry is missing a " at the end of the line
 +
 +
PASS: glexec-configure produces valid, working glexec.conf and lcmaps.db files
  
 
==== Savannah: https://savannah.cern.ch/bugs/?93190 ====
 
==== Savannah: https://savannah.cern.ch/bugs/?93190 ====
Line 434: Line 451:
  
 
FAILED: output is 0077 (internal umask setting for glexec)
 
FAILED: output is 0077 (internal umask setting for glexec)
 +
 +
==== Savannah: https://savannah.cern.ch/bugs/?101238 ====
 +
DESCRIPTION: mkgltempdir -t option does not work
 +
 +
REPRODUCE:
 +
    export X509_USER_PROXY=<location of valid proxy>
 +
    export GLEXEC_CLIENT_CERT=$X509_USER_PROXY
 +
    gldir=`/usr/sbin/mkgltempdir -t 404` && ls -ld $gldir && /usr/sbin/mkgltempdir -r $gldir
 +
 +
PASSED: lists directory with permissions dr-----r--
 +
 +
FAILED: gives error messages starting with /bin/chmod: cannot access `<directory name>': Permission denied

Latest revision as of 09:17, 19 April 2013

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