Fail, no fall-back when the user-provided singularity image is missing
User jobs specifying an image run only ono Glideins advertising HAS_SINGULARITY=True
Singularity can still fail for a number of reasons:
- misspelled user image path (or missing file)
- CVMFS hosting singularity or the image broke
The current behavior is to fall-back if the initial option allows
This should change in an error (consider singularity becoming REQUIRED if there is a user image specified).
The two options are a job failure (preferred by Marco and Mats because the most likely error is a wrong image path in the user job)
or a wrapper failure (this will cause the job to retry somewhere else).
#4 Updated by Marco Mambelli 23 days ago
Yes, GWMS_SINGULARITY_STATUS_EFFECTIVE (same as GWMS_SINGULARITY_STATUS_EFFECTIVE and other variables marked as "Dynamic" in https://glideinwms.fnal.gov/doc.prd/factory/custom_vars.html) are set and used within the scripts as a result of other variables set in Factory and frontend).
Merged to branch_v3_7.