|
| Date |
11.05.2009 |
| Priority |
Normal |
Description
glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-LFC_mysql, glite-LFC_oracle, glite-FTA_oracle, glite-FTS_oracle, glite-WN, glite-UI, glite-VOBOX
The new version of DPM and LFC contains a series of new features and bug fixes. See the packages described below for more details.
Known Issue
bug #49369: There is a known problem
when configuring DPM 1.7.0-6 using YAIM. For more details please visit the DPM disk and the DPM mysql.
LCG-DM 1.7.0-5
- srmCopy has been fully implemented
- WLCG SRM MoU requirements:
- support for multiple groups on spaces
- SRM2.2 srmReleaseFiles can be used without a requestToken
- srmLs can return information about the spaces in which a file resides
- new dpm-listspaces CLI, which will also serve as information provider
Note the 1.7 series of the DPM requires a database schema change with respect to earlier versions. The YAIM script will automatically do this.
However as a precaution the DPM databases should be backed up before doing the upgrade.
Starting with DPM version 1.7.0 the system includes the facility to provide lists of reserved space tokens to the information system. In the past
some user communities needed that information and to provide it the DPM admin may have been asked to add an information provider script.
As these additions were applied by hand an extra step is required to remove them. Therefore if a script was added one should remove it when
upgrading to version 1.7.0. In particular the 'glite-info-dpm-space-tokens' provider was quite commonly used. For that provider one should check
for the following files on the DPM head node and remove if necessary:
- /opt/glite/etc/gip/provider/glite-info-dpm-space-tokens-provider
- /opt/glite/libexec/glite-info-dpm-space-tokens
although the naming, in particular of the file in gip/provider/, may vary according the precise installation procedure that was followed.
DPM-DSI 1.7.0-1
- added ADLER32 and CRC32 checksum algorithms to CKSM handler
- Fixes #42623: DM custom packager creates rpms with invalid name
CGSI_gSOAP-2.7 v1.3.2-2
- Fixes #42623: DM custom packager creates rpms with invalid name
- gSOAP 2.7.10 has introduced a virtual destructor, which inserts
a pointer to the VMT at the beginning of the 'soap' structure,
making the C and C++ versions of the code binary incompatible,
so we need to build C++ flavour of the libraries as well with
_cpp suffix.
- Added new function, export_delegated_credentials(), to make
a delegated credential token available in memory suitable for
storage and later reuse by the user.
- Removed some spurious trailing newlines from error messages.
- Fixed descriptor and connection leak on the client side
when the authenitcation negociation to a server fails.
- Enhanced some error messages to cover more of the error message
recommendations in bug #35320.
glite-data-dpm-httpd-shell v1.2.1-2
- dpm-httpd-cmd, dpm-httpd-cp: fixing X509 environment variable names
X509_USERCERT->X509_USER_CERT ... similiar X509_USERKEY & X509_USERPROXY
- Checking the default proxy location in /tmp/x509up_u* as well.
glite-data-dpm-xrootd v2.0.3-1
- Fixes #42623: DM custom packager creates rpms with invalid name.
- Improving stability: initialise a couple of pointers in case DPM calls fail
- fix in logrotation script to check if dpm-xrd is actually configured
before sourcing the config file.
glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-LFC_mysql, glite-LFC_oracle, glite-WN, glite-UI, glite-VOBOX
This is an update of the DPM and LFC path fixing some outstading issues:
- Fix memory leak in dpm_get_max_get_lifetime()
- Correct problem with bug fix 40553 (dpm-drain)
- update dpm-listspaces to v1.3.1-4
glite-FTA_oracle, glite-FTS_oracle, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE
New version of the VOMS Java APIs to fix some bugs. Please, check the list of bugs in the specific service update pages for more information.
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 |
|
#30454 |
VOMS libraries doesn't use symlink |
|
#31041 |
{lfc,dpns}-get{usr,grp}map is missing |
|
#33640 |
DPM-http-client should be included into some metapackage |
|
#34205 |
[yaim lfc] bug in config_lfc_server |
|
#35320 |
CGSI_gSOAP: improving error messages |
|
#35431 |
DPM xrootd logrotate sources a file that does not exist |
|
#39947 |
Bug in org.glite.security.voms prevents building of dbgpthr flavors |
|
#40273 |
[DPM-client] dpm-drain migrates data out of spacetoken / pool |
|
#40500 |
DPM: multiple groups on spaces |
|
#40501 |
DPM: release file without request token |
|
#40553 |
[DPM]: dpm-drain should replicate non expired volatile files |
|
#40741 |
[LFC] Python interface does not work with Swig 1.3.24 |
|
#40746 |
[DPM] Add dpm-listspaces to repository/distribution |
|
#40927 |
[DPM] To remove file entries on some conditions |
|
#41883 |
VOMS Java API vulnerability - Fake any role |
|
#42623 |
DM custom packager creates rpms with invalid name |
|
#43106 |
YAIM does not configure /etc/sysconfig/rfiod properly on DPM |
|
#43306 |
[VOMS]: Memory leak in the api |
|
#43332 |
LFC does not compile with glibc 2.8 headers |
|
#44936 |
[VOMS 1.8.8-2] VOMS server stops handling requests after 8 hrs |
|
#45330 |
Problem with VOMS API Java: for some VOs the .lsc file is not considered |
|
#45711 |
DPM space token information provider fails if a space token does not have a group assigned |
|
#45812 |
DPM memory leak |
|
#45814 |
DPM: information provider can incorrectly report space token usage as 0 |
|
#46505 |
"certificate in chain has been revoked" error with voms-api-java |
|
#47090 |
VOMS_Init() breaks handling of new-style cert. proxies in Globus libraries |
Updated rpms
The RPMs can be updated using yum via
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)
|
