gLite 3.0
glite-LFC_oracle - Update to version 3.0.7-0
There is presently a known issue with this update of LFC/DPM. We recommend to either not update your LFC/DPM for the moment or apply the following workaround (also if you have already updated your system):
The upgrage of the LFC/DPM service (1.6.4-3) contains among others the following important new features and bug fixes:
This upgrade introduces new exceptions
No action is required by users and the R-GMA clients will be working as before.
Other upgrades
Incorrect apel-* dependencies have been removed from the metapackages to fix the GGUS ticket 16550.
Please also have a look at the list of known issues.
This update fixes various bugs. For the full list of bugs, please see list below.
glite-LFC_oracle - Update to version 3.0.7-0
| Date | 14.05.07 |
|---|---|
| Priority | High |
Description
There is presently a known issue with this update of LFC/DPM. We recommend to either not update your LFC/DPM for the moment or apply the following workaround (also if you have already updated your system):
mkdir -p /home/glbuild/GLITE_3_0_3_RC1_DATA/stage/etc
ln -s /opt/lcg/etc/lcgdm-mapfile \
/home/glbuild/GLITE_3_0_3_RC1_DATA/stage/etc
We will release a fix for this problem as soon as possible.
lcg-vomscerts
Important note:
The update of lcg-vomscerts has a new certificate for lcg-voms.cern.ch.
The current certificate will expire on May 29.
glite-yaim
This is an early release of the new modular release series and it
enables the new FTS and FTA configuration. The new configuration targets
FTA2 and FTS2 have to be used. That is, yaim should be run with options
-n FTS2 and/or -n FTA2.
Other new features of this update are the following:
- In site-info.def the VOAGENT_PYTHON agent type should be replaced with VOAGENT. All the defined typdefault variables should be changed correspondingly.
-
Two new YAIM variables are introduced. They are not compulsory to be set and
have default values as in the following:
This is to allow the usage of the same remote DB server serving several DPM node.# The DPM db name. Default is dpm_db DPM_DB=dpm_db # The DPNS db name. Default is cns_db DPNS_DB=cns_db
-
Important: apt-autoupdate not supported, i.e. do the upgrade and the reconfiguration
in one process. As always, it is recommended to do a DB backup before the upgrade.
-
Important: After the reconfiguration, DPM will use BDII as information
provider instead of MDS.
Because of this, the connect string and the port number on the site-BDII has to be changed
as follows:
-
from
"mds-vo-name=local,o=grid"
to"mds-vo-name=resource,o=grid" -
and from
2135to2170respectively.
Note: As a side effect of this reconfiguration the lcg-cr command will not work if your LCG_GFAL_INFOSYS variable is pointing to the DPM's infosys instead of a top-level BDII. This is not a bug, just a consequence worth to mention. -
from
The upgrage of the LFC/DPM service (1.6.4-3) contains among others the following important new features and bug fixes:
-
Added database migration scripts for DPM secondary groups support with the following new features:
- allow in srmMv to move a file to another directory giving the directory name as target
- if the free space in a pool or filesystem was already negative, it was still possible to reserve space
- report fileLocality in srmLs output (WLCG decision)
- return an error if attempt to extend lifetime of an already expired TURL
- python interface to DPNS - Fix garbage collector thresholds checks (was not working if poolfree space was negative, i.e. pool space overcommitted)
- The new information provider is BDII, so node firewall need to be changed, furthermore site-BDII needs reconfiguration. (Please, see the glite-yaim update above as well.)
This upgrade introduces new exceptions
RGMABusyException and
RGMANoWorkingReplicasException for R-GMA. These exceptions can
be thrown in a future server versions of R-GMA and this update will enable
rollout of clients that can handle this exception in readiness for a server
update.No action is required by users and the R-GMA clients will be working as before.
Other upgrades
Incorrect apel-* dependencies have been removed from the metapackages to fix the GGUS ticket 16550.
Please also have a look at the list of known issues.
This update fixes various bugs. For the full list of bugs, please see list below.
Fixed bugs
| Number | Description |
|---|---|
| #22355 | Remove incorrect dependencies on apel-* from metapackages |
Updated rpms
| Name | Version | Full RPM name | Description |
|---|---|---|---|
| glite-LFC_oracle | 3.0.7-0 | glite-LFC_oracle-3.0.7-0.noarch.rpm | gLite LFC Oracle node |
| glite-rgma-api-c | 5.0.10-1 | glite-rgma-api-c-5.0.10-1.i386.rpm | C API for R-GMA |
| glite-rgma-api-cpp | 5.0.15-1 | glite-rgma-api-cpp-5.0.15-1.i386.rpm | C++ API for R-GMA |
| glite-rgma-api-java | 5.0.5-1 | glite-rgma-api-java-5.0.5-1.noarch.rpm | Java API for R-GMA |
| glite-rgma-api-python | 5.0.12-1 | glite-rgma-api-python-5.0.12-1.noarch.rpm | Python API for R-GMA |
| glite-rgma-stubs-servlet-java | 5.0.9-1 | glite-rgma-stubs-servlet-java-5.0.9-1.noarch.rpm | Java client implementation stubs for R-GMA |
| glite-yaim | 3.0.1-15 | glite-yaim-3.0.1-15.noarch.rpm | glite-yaim |
| lcg-dm-common | 1.6.4-3sec | lcg-dm-common-1.6.4-3sec.i386.rpm | LCG Data Management common libraries and man pages. |
| lcg-vomscerts | 4.5.0-1 | lcg-vomscerts-4.5.0-1.noarch.rpm | lcg-vomscerts |
| LFC-client | 1.6.4-3sec | LFC-client-1.6.4-3sec.i386.rpm | Client side libraries for the LFC |
| LFC-interfaces | 1.6.4-3 | LFC-interfaces-1.6.4-3.i386.rpm | LCG File Catalog Interfaces |
| LFC-server-oracle | 1.6.4-3sec | LFC-server-oracle-1.6.4-3sec.i386.rpm | LFC Server for an Oracle database backend |
The RPMs can be updated using apt via
- via apt: apt-get dist-upgrade
- or via a download from:
http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/rhel30/RPMS.updates/
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Service must be restarted.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)