(r9) CreamTestsP4415 < EgeeJra1It

Tags: , view all tags
%TOC%

---+ *[[https://savannah.cern.ch/patch/index.php?4415][PATCH 4415]]*

---+++ Automatic tests

   * report #1:
      * CREAM UI version: 1.12.1; CREAM testsuite version: 1.0.7
      * Used direct polling for monitoring and BUpdater/BNotifier for status change detection
      * Batch system: TORQUE
      * All tests have been performed %RED%successfully%ENDCOLOR% (see the %RED%report%ENDCOLOR% from the testsuite)


Tested that the BDII is operational

<verbatim>
ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b o=infosys
</verbatim>

Output is %RED%here%ENDCOLOR%
Checked the Glue 1.3 root entry:

<verbatim>
ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b mds-vo-name=resource,o=grid
</verbatim>

Output is %RED%here%ENDCOLOR%

Checked the Glue 2.0 root entry:

<verbatim>
ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b o=glue
</verbatim>

Output is %RED%here%ENDCOLOR%


Information content check:

<verbatim>
$ gstat-validate-ce -H cream-42.pd.infn.it -p 2170 -b o=grid
OK - errors 0, warnings 0, info 0
</verbatim>

---+++ Checked bugs

   * Bug [[https://savannah.cern.ch/bugs/?54755][#54755]]: Could YAIM warn if a site tries to enable whole-VO FQANs? %GREEN%FIXED%ENDCOLOR%
      * Define a VO with the character "/" as a prefix in the variables [queue]_GROUP_ENABLE of the site-info.def
      * Run the YAIM configurator  and verify that in the output the following warning appears: "Queue [vo name] was enabled for one or more FQANs which specify an entire VO"

   * Bug [[https://savannah.cern.ch/bugs/?61396][#61396]]: CREAM and CEMon log4j.properties should take into account the value of GLITE_LOCATION_LOG %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?62078][#62078]]: Missing glite-pbsparser.log file on standalone Torque-Server %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?63007][#63007]]: CREAM sandbox dir should be relocatable %GREEN%FIXED%ENDCOLOR%
      * Define the variable CREAM_SANDBOX_PATH in the file services/glite-creamce
      * Reconfigure with YAIM, submit a job and verify that the sandbox of that job is placed into the new sandbox path

   * Bug [[https://savannah.cern.ch/bugs/?63956][#63956]]: config_cream_gip may use wrong VO %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?67238][#67238]]: !BUpdaterLSF problem with bhist failure %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?68225][#68225]]: In some cases the sudoers file created by yaim-cream-ce can be syntactically wrong %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?69785][#69785]]: Use #include to modify /etc/sudoer for CREAM with sudo >= 1.7.1 %GREEN%FIXED%ENDCOLOR%
      * With sudo version >= 1.7.1 installed, reconfigure with YAIM 
      * Verify that all CREAM directives are written into the file /etc/sudoers.forcream
      * Update from glite-CREAM version < 3.2.8, reconfigure with YAIM
      * Verify that the CREAM directives have been moved from the original /etc/sudoers file into the new /etc/sudoers.forcream

   * Bug [[https://savannah.cern.ch/bugs/?70285][#70285]]: it should be possible to tell bhist and tracejob how many logs to read %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?70287][#70287]]: Problem with !AssignFinalState if state is IDLE %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?70808][#70808]]: PBS submission script creates wrong stagein/stageout directives with qsub's -W option %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?71038][#71038]]: CE certificate publication error %GREEN%FIXED%ENDCOLOR%
      * Use a host certificate whose subject DN contains at least one blank character
      * Run the YAIM configurator and verify that the attribute !GlueServiceDataValue of the item <verbatim>
GlueServiceDataKey=DN,GlueServiceUniqueID=[unique ID for the CE],Mds-Vo-name=resource,o=grid
</verbatim> contains the complete DN

   * Bug [[https://savannah.cern.ch/bugs/?71055][#71055]]: !LL_ and !IL_ PIDFILE added more times in /opt/glite/etc/lb.conf  %GREEN%FIXED%ENDCOLOR%
      * Run more times the YAIM configurator and verify that the file /opt/glite/etc/lb.conf does not change.

   * Bug [[https://savannah.cern.ch/bugs/?71967][#71967]]: There should be in blah the option to set the temporary job work dir %RED%TODO%ENDCOLOR%
      * no comment

   * Bug [[https://savannah.cern.ch/bugs/?72097][#72097]]: cream-config.xml and cemonitor-config.xml should use GLITE_LOCATION_LOG and GLITE_LOCATION_VAR  %GREEN%FIXED%ENDCOLOR%
      * Define the variables GLITE_LOCATION_VAR=[new var directory] and CREAM_SANDBOX_PATH=[new sandbox dir] in the file services/glite-creamce
      * Run the YAIM configurator and verify that the new var directory is specified into the following attributes:
         * cream-config.xml: cream_scratch_dir, cream_sandbox_dir, delegation_storage, CREAM_SANDBOX_DIR, JOBS_SCRATCH_DIR
         * cemonitor-config.xml: backendLocation

   * Bug [[https://savannah.cern.ch/bugs/?72508][#72508]]: variable CREAM_DB_PASSWORD missed in services/glite-creamce %GREEN%FIXED%ENDCOLOR%
      * Verify that the file ${GLITE_LOCATION}/yaim/examples/siteinfo/services/glite-creamce contains the variable CREAM_DB_PASSWORD

   * Bug [[https://savannah.cern.ch/bugs/?72756][#72756]]: glite-ce-blahparser missed in gLiteservices %GREEN%FIXED%ENDCOLOR%
      * Stop all the gLite service on the CE
      * Remove the script glite-ce-blahparser from the gLiteservices list
      * Reconfigure with YAIM and verify that the glite-ce-blahparser has been re-inserted into the list


---+++ Clean installation

   * Installation steps:<verbatim>
wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4415_2/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
yum install xml-commons-apis
yum install glite-CREAM
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_utils.repo -O /etc/yum.repos.d/glite-TORQUE_utils.repo
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_server.repo -O /etc/yum.repos.d/glite-TORQUE_server.repo
yum install glite-TORQUE_utils glite-TORQUE_server
/opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
</verbatim>
   * View the [[%ATTACHURL%/yum_install_log.txt.gz][log]] of yum for a clean installation 
   * View the [[%ATTACHURL%/yaim_install_log.txt.gz][log]] of yaim for a clean installation (TORQUE is used)

---+++ Upgrade from production
   * Upgrade steps:<verbatim>
wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4415_2/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
yum update
/opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
</verbatim>
   * View the [[%ATTACHURL%/yum_update_log.txt.gz][log]] of yum for an upgrade
   * View the [[%ATTACHURL%/yaim_update_log.txt.gz][log]] of yaim for an upgrade (TORQUE is used)
Attachments
Topic attachments
I	Attachment	Action	Size	Date	Who	Comment
gz	yaim_install_log.txt.gz	manage	19.7 K	2010-10-19 - 14:17	PaoloAndreetto	YAIM installation log
gz	yaim_update_log.txt.gz	manage	16.4 K	2010-10-19 - 14:18	PaoloAndreetto	YAIM update log
gz	yum_install_log.txt.gz	manage	9.3 K	2010-10-19 - 14:16	PaoloAndreetto	YUM installation log
gz	yum_update_log.txt.gz	manage	1.0 K	2010-10-19 - 14:17	PaoloAndreetto	YUM update log
Topic revision: r9 - 2010-10-19 - PaoloAndreetto
Account
- Log In
~~Edit~~
~~Attach~~