This wiki is obsolete, see the NorduGrid web pages for up to date information.
Testing EMI 1.0.1 rc4/ARC-Core
Component:
Savanah task: https://savannah.cern.ch/task/?20925
ETICS Configuration name:
VCS TAG:
EMI Release:
Platform:
Author:
Date:
Deployment tests
Clean Instalation
Upgrage installation
Static code Analysis
Unit Test Execution
Regression tests
Bug #2442
Tester: Florido thanks to Andrii Status: DRAFT
-Description of problem (for example description of bug with link to bugzilla)
All voms proxies created by lcg-voms.cern.ch (ops/atlas/etc..) produce this error when connecting to gridftp.
[2011-05-26 10:41:38] [Arc.Credential] [WARNING] [12746/406270720] VOMS: the holder serial number 167235872 is not the same as the serial number in AC 4943
The problem does not show up for other vomses.
http://bugzilla.nordugrid.org/cgi-bin/bugzilla/show_bug.cgi?id=2442
-Test scenario (all details needed to reproduce test)
- Test scenario (all details needed to reproduce test)
Prerequisites:
- an ARC server with [groups] configured for VOMS
- a grid identity member of some VO serverd by VOMS
- access to some MyProxy server
- voms and myproxy clients installed
- Generate proxy with VOMS AC extension directly from EEC using arcproxy, then
using voms-proxy-init tool (I will specify command only, all output would be so
long):
[manf@n5 ~]$ arcproxy --voms testbed.univ.kiev.ua [manf@n5 ~]$ arcproxy -O --voms testbed.univ.kiev.ua [manf@n5 ~]$ voms-proxy-init -voms testbed.univ.kiev.ua [manf@n5 ~]$ voms-proxy-init -old -voms testbed.univ.kiev.ua [manf@n5 ~]$ voms-proxy-init -rfc -voms testbed.univ.kiev.ua
- Upload delegation to MyProxy, then retreive it and get VOMS AC extension for
new proxy.
Upload:
[manf@n5 ~]$ voms-proxy-init -old -voms testbed.univ.kiev.ua
Retreive:
[manf@n5 ~]$ myproxy-logon -s grid.org.ua -l manf -m testbed.univ.kiev.ua
-
With this two types of proxies, you need to:
- Simply check ARC VOMS API works (you must see VOMS AC information instead of
errors):
[manf@n5 ~]$ arcproxy --info Subject: /DC=org/DC=ugrid/O=people/O=KNU/CN=Andrii Salnikov/CN=2005159956/CN=491292708/CN=153469402/CN=153469402 Identity: /DC=org/DC=ugrid/O=people/O=KNU/CN=Andrii Salnikov Time left for proxy: 10 hours 59 minutes 57 seconds Proxy path: /tmp/x509up_u1000 Proxy type: X.509 Proxy Certificate Profile RFC compliant impersonation proxy - RFC inheritAll proxy ====== AC extension information for VO testbed.univ.kiev.ua ====== Attribute: /voname=testbed.univ.kiev.ua/hostname=grid.org.ua:15112/testbed.univ.kiev.ua:nickname=manf Attribute: /voname=testbed.univ.kiev.ua/hostname=grid.org.ua:15112 Attribute: /testbed.univ.kiev.ua Attribute: /testbed.univ.kiev.ua/t_test Timeleft for AC: 11 hours 57 minutes 39 seconds
- Submit a simple job (it would be great if you configure access filtering by VOMS AC, see my previous comments regarding reproducing it via [group] configuration), check gridftp logs for errors, retrieve job results.
- Simply check ARC VOMS API works (you must see VOMS AC information instead of
errors):
-Infrastructure used to perform test (for example testbed with specification of software)
You need to do all general things regarding job submit to ARC, just do it with
different proxy certificates.
> -Expected results All must works smoothly instead of getting errors :-)
> -Output of test (for example stdout, stderr) I would be a lot of output, and I cannot provide example with errors anymore, because of updating machine where I had perfomed the tests to 1.0.1rc4.
Just review my previous comments for this bug and bug #2520 and you can find some example.
-Comments and proposals (should be used as feedback for developers) -The final decision PASSED/FAILED