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: both TORQUE and LSF. Two different CEs one submitting to Torque (cream-33) and one submitting to LSF (cream-26)
- All tests have been performed successfully (see the report from the testsuite)
Information service checks
Tested that the BDII is operational
ldapsearch -x -h cream-33.pd.infn.it -p 2170 -b o=infosys
Output is
here
Checked the Glue 1.3 root entry:
ldapsearch -x -h cream-33.pd.infn.it -p 2170 -b mds-vo-name=resource,o=grid
Output is
here
Checked bugs
- Bug #75369
: [yaim-cream-ce] Reconfiguration with yaim produces garbled sudoers file
- Reproduced the bug configuring from scratch and then re-configuring a cream-ce using files users.conf
and groups.conf
attached to GGUS ticket 64189
- Applied the fix, cleaned the sudoers file, verified that re-configuration does not spoil /etc/sudoers file
- Bug #75029
: Error when GLITE_LOCATION_LOG is differet from default FIXED
- set GLITE_LOCATION_LOG=/tmp/test
- create /tmp/test as root
- verify that yaim stops with message "ERROR: GLITE_LOCATION_LOG directory /tmp/test exists but it is not writable by tomcat user"
- chown tomcat:tomcat /tmp/test
- verify that yaim complete configuration without errors
Clean installation
- Installation issues
- Due to a malfunctioning of the official jpackage mirrors the following repository has been used:
[jpackage5-generic]
name=JPackage 5, generic
baseurl=http://devel12.cnaf.infn.it:7444/repository/jpackage-free/
enabled=1
protect=1
- Due to a malfunctioning of the official dag mirrors the following repository has been used:
### Name: RPMforge RPM Repository for RHEL 4 - dag
### URL: http://rpmforge.net/
[rpmforge]
name = RHEL $releasever - RPMforge.net - dag
baseurl = http://apt.sw.be/redhat/el4/en/$basearch/rpmforge
mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge
#mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge
enabled = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
gpgcheck = 1
[rpmforge-extras]
name = RHEL $releasever - RPMforge.net - extras
baseurl = http://apt.sw.be/redhat/el4/en/$basearch/extras
mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge-extras
#mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-extras
enabled = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
gpgcheck = 1
[rpmforge-testing]
name = RHEL $releasever - RPMforge.net - testing
baseurl = http://apt.sw.be/redhat/el4/en/$basearch/testing
mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge-testing
#mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-testing
enabled = 0
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
gpgcheck = 1
- This repository has been obtained following the procedure below:
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el4.rf.i386.rpm
rpm -ihv rpmforge-release-0.5.1-1.el4.rf.i386.rpm
yum update
enable = 1 for [rpmforge-extras] repository in /etc/yum.repos.d/rpmforge.repo
Upgrade from production
--
SaraBertocco - 2010-12-07