Incorrect behavior of Singularity
Singularity problems were reported:
We had report from T1 & T2 IN2P3 which their entries that connected to worker nodes with SL6 failing to run jobs owing to set up HAS_SINGULARITY=True. These site has no singularity set up on their SL6 farm.
Singularity ends up being enabled also when it should not:
Wed Mar 14 21:17:27 CET 2018 GLIDEIN_Singularity_Use not configured. Defaulting it to NEVER Wed Mar 14 21:17:27 CET 2018 GLIDEIN_SINGULARITY_REQUIRE not configured. Defaulting it to False Wed Mar 14 21:17:27 CET 2018 Factory requires glidein to use singularity: False Wed Mar 14 21:17:27 CET 2018 VO's desire to use singularity: NEVER Wed Mar 14 21:17:27 CET 2018 Entry configured with singularity: NONE Wed Mar 14 21:17:27 CET 2018 VO does not want to use singularity HAS_SINGULARITY = True
Jeff Dost suggested a patch:
--- singularity_setup.sh.orig 2018-03-16 09:16:04.234614984 -0700 +++ singularity_setup.sh 2018-03-16 09:17:01.801662403 -0700 @@ -179,6 +179,7 @@ no_use_singularity_config exit 1 fi + no_use_singularity_config ;; OPTIONAL) #GWMS Even in OPTIONAL case, FE will have to specify the wrapper script if [ "$require_singularity" = "True" ]; then
#1 Updated by Marco Mambelli almost 2 years ago
- Status changed from New to Feedback
- Assignee changed from Marco Mambelli to Dennis Box
After reviewing Jeff suggestion and the scripts I proposed a different solution that fixes the behavior of singularity_setup.sh and adds an option that allows not to interfere with VO setting up singularity independently. This option can be selected in the Frontend GLIDEIN_Singularity_Use=DISABLE_GWMS and is the default. Previously the default was NEVER, now all the other 3 values NEVER, OPTIONAL, REQUIRED have to be selected explicitly if desired.
default_singularity_wrapper.sh has been improved and made more robust (will run OK also when running but Singularity is not selected).
Documentation has been updated.
Changes in v3/19429
Branched from v3_2_21_post, not branch_v3_2