[ARVADOS] updated: 2.1.0-1672-g8529a9c53

Git user git at public.arvados.org
Mon Nov 22 18:45:32 UTC 2021


Summary of changes:
 doc/admin/upgrading.html.textile.liquid | 4 ++++
 1 file changed, 4 insertions(+)

       via  8529a9c53dae3a457f6dbce8aab22571b5837fac (commit)
       via  1f56c3fa3ecb12a252d77ab45b81e7a27015bd4f (commit)
      from  db8fac04e5a7fb21bb91be59c507d6771e50c85a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 8529a9c53dae3a457f6dbce8aab22571b5837fac
Merge: db8fac04e 1f56c3fa3
Author: Tom Clegg <tom at curii.com>
Date:   Mon Nov 22 13:45:21 2021 -0500

    Merge branch '18298-lsf-no-suitable-hosts'
    
    refs #18298
    
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at curii.com>


commit 1f56c3fa3ecb12a252d77ab45b81e7a27015bd4f
Author: Tom Clegg <tom at curii.com>
Date:   Mon Nov 22 13:44:41 2021 -0500

    18298: Add upgrade note re updated default BsubArgumentsList.
    
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at curii.com>

diff --git a/doc/admin/upgrading.html.textile.liquid b/doc/admin/upgrading.html.textile.liquid
index 1302bdf42..517c2dd0c 100644
--- a/doc/admin/upgrading.html.textile.liquid
+++ b/doc/admin/upgrading.html.textile.liquid
@@ -39,6 +39,10 @@ h2(#main). development main (as of 2021-11-10)
 
 "previous: Upgrading from 2.3.0":#v2_3_0
 
+h3. Default LSF arguments have changed
+
+If you use LSF and your configuration specifies @Containers.LSF.BsubArgumentsList@, you should update it to include the new arguments (@"-R", "select[mem>=%MMB]", ...@, see "configuration reference":{{site.baseurl}}/admin/config.html). Otherwise, containers that are too big to run on any LSF host will remain in the LSF queue instead of being cancelled.
+
 h3. Previously trashed role groups will be deleted
 
 Due to a bug in previous versions, the @DELETE@ operation on a role group caused the group to be flagged as trash in the database, but continue to grant permissions regardless. After upgrading, any role groups that had been trashed this way will be deleted. This might surprise some users if they were relying on permissions that were still in effect due to this bug. Future @DELETE@ operations on a role group will immediately delete the group and revoke the associated permissions.

-----------------------------------------------------------------------


hooks/post-receive
-- 




More information about the arvados-commits mailing list