Differences

This shows you the differences between two versions of the page.

--- oar_2.5.4 [2015/04/13 16:56] – [Errata / Known bugs] neyron
+++ oar_2.5.4 [2015/11/06 17:44] (current) – neyron
@@ Line 15: / Line 15: @@
   * [kamelot] BUGFIX: fix hierarchies manipulation (remove toplevel resource).
   * [accounting] Fixed a memory leak and a rare case of bad consumption count.
-  * [almighty] Rewrote the handling of finished oarexec: launch bipbip processes with MAX_CONCURRENT_JOB_TERMINATIONS to not overload the server.
+  * [oar.conf] Replace the MAX_CONCURRENT_JOB_TERMINATIONS option by MAX_CONCURRENT_JOBS_STARTING_OR_TERMINATING
+  * [almighty] Rewrote the handling of starting and finishing jobs: limit bipbip processes to MAX_CONCURRENT_JOBS_STARTING_OR_TERMINATING to avoid overloading the server.
   * [oarexec] Introduced BASH_ENV=~oar/.batch_job_bashrc for batch jobs Batch jobs with bash shell have some difficulties to source the right bash scripts when launching. Now we set BASH_ENV=~oar/.batch_job_bashrc before launching the user bash process so we can handle which script must be sourced. By default we source ~/.bashrc.
   * [commands] Exit immediately on wrong arguments.
@@ Line 56: / Line 57: @@
   * If upgrading from OAR 2.5.2 or OAR 2.5.3, you will be exposed to a bug with OAR database schema version which causes ''oar-database --upgrade'' to report an error. Please read the page [[wiki:fix for database schema version 2.5.0]].
   * If upgrading from a previous version of OAR, apt-get and yum will complain about the ''oar-admin'' package which conflicts with the installation of the ''oar-user'' 2.5.4 package. This is normal: the ''oar-admin'' package must be removed (''oar-admin'' is not compatible with OAR 2.5.4, see the ''oar_resources_add'', ''oar_resources_init'' and ''oaradmissionrules'' commands instead).
-  * A bug was discovered regarding the storage of the pidfile of the oar-node service (file ''/var/lib/.pid'' instead of ''/var/lib/oar-node.pid''). This is harmless.
+  * [fixed] A bug was discovered regarding the storage of the pidfile of the oar-node service (file ''/var/lib/.pid'' instead of ''/var/lib/oar-node.pid''). This is harmless.
-  * A bug was discovered with advance reservations when moldable jobs are used.
+  * [fixed] A bug was discovered with advance reservations when moldable jobs are used.
-  * **A bug was discovered with OAR database backend (MySQL or PostgreSQL) and the TRUNCATE queries**.
+  * [fixed] **A bug was discovered with OAR database backend (MySQL or PostgreSQL) and the TRUNCATE queries**.
   * A bug was discovered when using some long options of the ''oar_resources_add'' command. The counterpart short options works.
+  * A bug was discovered when modifying admission rules with the ''oaradmissionrules'' command, when MySQL is the database backend.
 Please note that PostgreSQL is the preferred database backend, for performance reasons. MySQL support will be deprecated/dropped in next versions. Therefore, for new installs, please prefer PostgreSQL.
-===== Updates ======
+**New packages are released and fix the major issues discussed above (tagged with [fixed]) :**
-**New packages are released and fix the major issues discussed above:**
+  * Sources: the 2.5.4.1 tarball encompasses the fixes.
-  * Sources: the 2.5.4.1 tarball encompasses all fixes.
+  * Debian: the 2.5.4-2 (jessie) and 2.5.4-2~bpo70+1 (wheezy-backports) deb packages encompass the fixes.
-  * Debian: the 2.5.4-2 (jessie) and 2.5.4-2~bpo70+1 (wheezy-backports) deb packages encompass all fixes.
+  * Centos6: the 2.5.4-3 rpm packages encompass the fixes.
-  * Centos6: the 2.5.4-3 rpm packages encompass all fixes.