Closed mambelli closed 3 months ago
@mambelli was the factory knob CVMFS_SRC
defined in the factory configuration file?
<attr name="CVMFS_SRC" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="osg"/>
My previous comment was irrelevant to what the actual problem was. Regardless of whether CVMFS_SRC
was used or not, the execution of cvmfsexec_platform_select.sh
should not occur if on-demand CVMFS will not be used (absence of GLIDEIN_USE_CVMFSEXEC
attribute in factory config) or if it has not been requested by the user/job (GLIDEIN_USE_CVMFSEXEC
set to 0
in factory config).
Marco clarified that the glidein setup that failed did not want to use the on-demand CVMFS provisioning, which basically meant that it was a vanilla factory configuration.
Describe the bug Glideins are failing in the version currently in the master branch because
cvmfsexec_platform_select.sh
is failing (exiting w/ non 0 exit code) during initial validation of custom scripts.In stderr you can see:
And in stdout:
To Reproduce Run the workspaces (latest version) linked to master from GitHub
Expected behavior Successful run-test.sh
Screenshots NA
Info (please complete the following information): Stakeholders and components can be a comma-separated list or on multiple lines. If you add a new stakeholder or component, not on the sample list, add it on a line by its own.
Additional context No release possible until this is fixed