General news
No news.
Release status
- UMD 4.16.2 released on May 13th https://repository.egi.eu/UMD/4.16.2.html
Known Errors Database KEDB
The KEDB has been moved to Jira+Confluence: list of known errors
- STORM: storm-webdav may ignore part of VO map https://ggus.eu/index.php?mode=ticket_info&ticket_id=151396
- dCache: dcache-srmclient and srmcp not compatible with JRE 1.8.0 https://ggus.eu/?mode=ticket_info&ticket_id=153984
- VOMS-Admin: MariaDB for voms-admin or StoRM must use timezone supported by Java https://ggus.eu/index.php?mode=ticket_info&ticket_id=151940
Status and actions
- List made by Maarten and Alessandro: https://docs.google.com/document/d/12nVv01eg1fGgbiCz2ediHo0yTcBFxEgkqYtTpcDk2W4/edit
- Next step: agree on a timeline
- Issue with HTTP links not redirected to HTTPS → FIXED
- HTCondor 9.0.12 in the queue (untested) for next release
Product teams
- GCT: OpenSSL 3 in RHEL 9 / Centos Stream 9 considers the sha1 hash to be too weak, and will not accept it. Part of the communication between the myproxy client and myproxy server uses sha1. An updated myproxy version that supports sha256 was released in EPEL.
- If you are running a myproxy server and wish to be able to accept requests from a client on a RHEL 9 / CentOS Stream 9 system you need to update your server. The new server still accepts request from old clients.
- If you are using a myproxy client and wish to be able to connect to a myproxy server running on a RHEL 9 / CentOS Stream 9 system you need to update your client. The new clients can still connect to old servers.
- In addition to the myproxy RPMS also the globus-gsi-proxy-core RPMS need updating.
- There was briefly a backward incompatible myproxy version in EPEL (6.2.9-7) due to an incomplete fix for this issue - do not use it.
AOB
Next meeeting April 18th