Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "UMD-2:UMD-2.1.0"

From EGIWiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}
{{Template:Middleware_menubar}}
{{TOC_right}}
[[Category:Middleware]]
[[Category:UMD]]
= '''UMD 2.1.0 : Additional information for provided products'''  =
= '''UMD 2.1.0 : Additional information for provided products'''  =


Line 14: Line 20:
**Detailed release notes: [https://twiki.cern.ch/twiki/bin/view/EMI/EMI2Final#EMI_UI_v_2_0_0_task_23322 EMI-UI 2.0.0 release notes]  
**Detailed release notes: [https://twiki.cern.ch/twiki/bin/view/EMI/EMI2Final#EMI_UI_v_2_0_0_task_23322 EMI-UI 2.0.0 release notes]  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No known issues.  
*'''Known Issues:'''  
**Bug in glite-wms-job-logging -i : https://ggus.eu/ws/ticket_info.php?ticket=86052
***https://wiki.italiangrid.it/twiki/bin/view/IGIRelease/Task23322
***add a missing parameter in row 240 in file /usr/bin/glite-wms-job-logging-info
**Problems with ARC 1.1.1 CEs and ARC 2.0.0 clients, especially with SLURM as the backend. Expected to be solved in the next update of ARC. You may need to downgrade the ARC clients to 1.1.1
*'''Version:''' 2.0.0
*'''Version:''' 2.0.0


Line 75: Line 85:
**Authorization problem with argus (pcks#8 keys). Problem is related with a known bug in bouncycastle [http://www.bouncycastle.org/jira/browse/BJA-400 bug] which prevents the CREAM authorization to be correctly initialized if the format of private key is pkcs#8 instead of the old format (pkcs#1). [https://ggus.eu/tech/ticket_show.php?ticket=83329 here]  
**Authorization problem with argus (pcks#8 keys). Problem is related with a known bug in bouncycastle [http://www.bouncycastle.org/jira/browse/BJA-400 bug] which prevents the CREAM authorization to be correctly initialized if the format of private key is pkcs#8 instead of the old format (pkcs#1). [https://ggus.eu/tech/ticket_show.php?ticket=83329 here]  
***Workaround: re-process the private key on SL6 with the following command: "openssl rsa -in hostkey.pem -out newhostkey.pem"  
***Workaround: re-process the private key on SL6 with the following command: "openssl rsa -in hostkey.pem -out newhostkey.pem"  
**Involuntary recreation of cremdb: https://ggus.eu/tech/ticket_show.php?ticket=85970
***Workaround: https://wiki.italiangrid.it/twiki/bin/view/CREAM/KnownIssues#Problem_by_submitting_jobs_via_W
*'''Version:''' 1.14.0
*'''Version:''' 1.14.0


Line 83: Line 95:
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details [https://ggus.eu/ws/ticket_info.php?ticket=82899 here].  
*'''Known Issues:''' SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details [https://ggus.eu/ws/ticket_info.php?ticket=82899 here].  
**This issue is solved in SAM Update '''17.1'''. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1
**This issue is solved in SAM Update '''17.1'''. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1  
**Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only ''after'' the NGI SAM box us updated to Update 17.1 or newer.
**Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only ''after'' the NGI SAM box us updated to Update 17.1 or newer.  
**It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: <code>vi /etc/emi-version</code> file and use EMI1 version: 1.11.0-1, but EGI ''strongly recommend'' to wait for the SAM Update 17.
**It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: <code>vi /etc/emi-version</code> file and use EMI1 version: 1.11.0-1, but EGI ''strongly recommend'' to wait for the SAM Update 17.  
*'''Version:''' 2.0.0
*'''Version:''' 2.0.0


Line 143: Line 155:
**Detailed release notes: [http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/9AgN/content/update-1-20-07-2012#BDII_top_v_1_0_2_task_30155 EMI bdii-top 1.0.2 release notes]  
**Detailed release notes: [http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/9AgN/content/update-1-20-07-2012#BDII_top_v_1_0_2_task_30155 EMI bdii-top 1.0.2 release notes]  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' The cron job that updates the BDII endpoints, executes a sleep command meaning that the top-urls.conf in some case can take some time [https://savannah.cern.ch/bugs/index.php?96484 here].
*'''Known Issues:''' The cron job that updates the BDII endpoints, executes a sleep command meaning that the top-urls.conf in some case can take some time [https://savannah.cern.ch/bugs/index.php?96484 here].  
** Workaround: After yaim configuration run: /usr/bin/glite-info-update-endpoints -c /etc/glite/glite-info-update-endpoints.conf > /var/log/glite/glite-info-update-endpoints.log 2>&1  
**Workaround: After yaim configuration run: /usr/bin/glite-info-update-endpoints -c /etc/glite/glite-info-update-endpoints.conf &gt; /var/log/glite/glite-info-update-endpoints.log 2&gt;&amp;1


*'''Version:''' 1.0.2
*'''Version:''' 1.0.2
Line 155: Line 167:
**Detailed release notes: [https://twiki.cern.ch/twiki/bin/view/EMI/EMI2Final#EMI_UI_v_2_0_0_task_23322 EMI-UI 2.0.0 release notes]  
**Detailed release notes: [https://twiki.cern.ch/twiki/bin/view/EMI/EMI2Final#EMI_UI_v_2_0_0_task_23322 EMI-UI 2.0.0 release notes]  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' No known issues.  
*'''Known Issues:'''  
**Bug in glite-wms-job-logging -i&nbsp;: https://ggus.eu/ws/ticket_info.php?ticket=86052
***https://wiki.italiangrid.it/twiki/bin/view/IGIRelease/Task23322
***add a missing parameter in row 240 in file /usr/bin/glite-wms-job-logging-info
**Problems with ARC 1.1.1 CEs and ARC 2.0.0 clients, especially with SLURM as the backend. Expected to be solved in the next update of ARC. You may need to downgrade the ARC clients to 1.1.1
*'''Version:''' 2.0.0
*'''Version:''' 2.0.0


Line 217: Line 233:
*'''Known Issues:'''  
*'''Known Issues:'''  
**There is Wrong lowercase conversion for VO Tags (both glue 2 and glue 1) [https://ggus.eu/tech/ticket_show.php?ticket=84509 here] - affects all cream-ce's  
**There is Wrong lowercase conversion for VO Tags (both glue 2 and glue 1) [https://ggus.eu/tech/ticket_show.php?ticket=84509 here] - affects all cream-ce's  
***workaround: not known
***workaround: not known  
 
**Involuntary recreation of cremdb: https://ggus.eu/tech/ticket_show.php?ticket=85970
***Workaround: https://wiki.italiangrid.it/twiki/bin/view/CREAM/KnownIssues#Problem_by_submitting_jobs_via_W
*'''Version:''' 1.14.0
*'''Version:''' 1.14.0


Line 227: Line 244:
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Installation Notes:''' No issues found during EGI's Software Provisioning.  
*'''Known Issues:''' SAM tests will fail for SAM versions &lt; = 16 (Solved in SAM 17.1). For details [https://ggus.eu/ws/ticket_info.php?ticket=82899 here].  
*'''Known Issues:''' SAM tests will fail for SAM versions &lt; = 16 (Solved in SAM 17.1). For details [https://ggus.eu/ws/ticket_info.php?ticket=82899 here].  
**This issue is solved in SAM Update '''17.1'''. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1
**This issue is solved in SAM Update '''17.1'''. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1  
**Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only ''after'' the NGI SAM box us updated to Update 17.1 or newer.
**Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only ''after'' the NGI SAM box us updated to Update 17.1 or newer.  
**It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: <code>vi /etc/emi-version</code> file and use EMI1 version: 1.11.0-1, but EGI ''strongly recommend'' to wait for the SAM Update 17.
**It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: <code>vi /etc/emi-version</code> file and use EMI1 version: 1.11.0-1, but EGI ''strongly recommend'' to wait for the SAM Update 17.  
*'''Version:''' 2.0.0
*'''Version:''' 2.0.0


Line 297: Line 314:
*'''Version:''' 5.2.1
*'''Version:''' 5.2.1


= Debian 6 =
= Debian 6 =


== emi.unicore-client6.debian-squeeze.amd64  ==
== emi.unicore-client6.debian-squeeze.amd64  ==

Latest revision as of 10:41, 19 February 2013

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Middleware menu: Home Software Calendars Technology Providers UMD Release Schedule UMD Products Overview UMD Products ID Cards Release and deployment process Middleware Requirements Next middleware release


UMD 2.1.0 : Additional information for provided products

While undergoing the EGI Software Provisioning process, some installation issues and known problems were detected and documented. This document provides the same information, in one single place, where site admins may learn about the provided software prior to installation or, with later updates to UMD-2, upgrading their systems.

Each section that follows will be linked by the relevant sections provided in the EGI Software Repository for this release of UMD.



Scientific Linux 6

emi.emi-ui.sl6.x86_64

emi.cluster.sl6.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since it is been included in the CREAM release in this UMD.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.unicore-client6.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 5.0.0

emi.unicore-xuudb.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 1.3.2-4

emi.unicorex6.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version:5.0.0

emi.cream-lsf.sl6.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since the same version as in SL5 OS.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.cream-torque.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.cream.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues:
  • Version: 1.14.0

emi.emi-wn.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details here.
    • This issue is solved in SAM Update 17.1. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1
    • Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only after the NGI SAM box us updated to Update 17.1 or newer.
    • It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: vi /etc/emi-version file and use EMI1 version: 1.11.0-1, but EGI strongly recommend to wait for the SAM Update 17.
  • Version: 2.0.0

emi.torque-server.sl6.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since the same version as in SL5 OS.
  • Known Issues: No known issues.
  • Version: 1.0.0-2

emi.torque-wn.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details here.
    • Workaround: vi /etc/emi-version file and use EMI1 version: 1.11.0-1.
  • Version: 1.0.0

emi.glexec-wn.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No Known issues.
  • Version: 1.1.1

emi.storm.sl6.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since the same version as in SL5 OS.
  • Known Issues: For storm SL6 installations there is a known problem with the mysql-connector-java package from sl6 security repository invalidates /usr/share/java/storm-backend-server/mysql-connector-java-5.1.12.jar.
    • Workaround is provided here.
  • Version: 1.10.0

emi.blah.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version:1.18.1

emi.gsoap-gss.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 3.1.4

emi.bdii-top.sl6.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: The cron job that updates the BDII endpoints, executes a sleep command meaning that the top-urls.conf in some case can take some time here.
    • Workaround: After yaim configuration run: /usr/bin/glite-info-update-endpoints -c /etc/glite/glite-info-update-endpoints.conf > /var/log/glite/glite-info-update-endpoints.log 2>&1
  • Version: 1.0.2

Scientific Linux 5

emi.emi-ui.sl5.x86_64

emi.unicorex6.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version:5.0.0

emi.unicore-xuudb.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 1.3.2-4


emi.unicore-client6.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 5.0.0


emi.cluster.sl5.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since it is been included in the CREAM release in this UMD.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.cream-lsf.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.cream-torque.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 2.0.0

emi.cream.sl5.x86_64

emi.emi-wn.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details here.
    • This issue is solved in SAM Update 17.1. The update has already successfully passed the staged rollout and will be announced in the days subsequent to the release of UMD 2.1
    • Monitoring the WN v2.0.0 with a SAM Update 16 - or older - will affect the site availability. Please, coordinate with your NGI to make sure that the WN are deployed only after the NGI SAM box us updated to Update 17.1 or newer.
    • It is possible to monitor the WNv2.0.0 with SAM 16 applying this workaround: vi /etc/emi-version file and use EMI1 version: 1.11.0-1, but EGI strongly recommend to wait for the SAM Update 17.
  • Version: 2.0.0

emi.torque-server.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 1.0.0-2

emi.torque-wn.sl5.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since the same version as in SL6 OS.
  • Known Issues: SAM tests will fail for SAM versions < = 16 (Solved in SAM 17.1). For details here.
    • Workaround: vi /etc/emi-version file and use EMI1 version: 1.11.0-1.
  • Version: 1.0.0

emi.glexec-wn.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No Known issues.
  • Version: 1.1.1

emi.storm.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.10.0

emi.blah.sl5.x86_64

  • Additional Details:
  • Installation Notes: Software Provisioning has not been performed for this release since the same version as in SL6 OS.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version:1.18.1

emi.gsoap-gss.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 3.1.4

emi.bdii-top.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 1.0.2

ige.globus-gram5.sl5.x86_64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version: 5.2.1

Debian 6

emi.unicore-client6.debian-squeeze.amd64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues: No known issues.
  • Version: 5.0.0

emi.unicore-xuudb.debian-squeeze.amd64

  • Additional Details:
  • Installation Notes: No issues found during EGI's Software Provisioning.
  • Known Issues:
    • Permissions for the /var/log/unicore directory have to be changed to 755: GGUS #83342
      • Workaround: chmod -R 755 /var/log/unicore
    • the xuudb-server.config file provided with the debian package of the XUUDB does not contain the host definition line here.
      • Workaround: add into xuudb-server.config file the host definition xuudb_http_host=https://.... (full qualified hostname)
  • Version: 1.3.2-4

emi.unicorex6.debian-squeeze.amd64

  • Additional Details:
  • Installation Notes: After Installation of the Debian owner and permission setting for the UNICORE component directories and file are inconsistent:
  • Known Issues: permission setting for the UNICORE component directories and file are inconsistent here.
    • Workaround: chown unicore:unicore /var/log/unicore;chown unicore:unicore /var/lib/unicore/unicorex; chmod -R 755 /var/log/unicore
  • Version:5.0.0