After cvmfsexec distributions have been built and then disabled (shows a warning), the work directory for cvmfsexec -- the one that contains the cvmfsexec distributions and programmatically initialized to glidein_cvmfsexec_dir=CVMFSEXEC_DIR -- turns out to be empty. This causes the on-demand cvmfs setup to fail even though there might be valid cvmfsexec distributions from a previous reconfig/upgrade of the factory since the directory is not visible to the factory (tested this for mode 2 of cvmfsexec only).
THIS IS A KNOWN ISSUE WITH GLIDEINWMS >= 3.10.2
After cvmfsexec distributions have been built and then disabled (shows a warning), the work directory for cvmfsexec -- the one that contains the cvmfsexec distributions and programmatically initialized to
glidein_cvmfsexec_dir=CVMFSEXEC_DIR-- turns out to be empty. This causes the on-demand cvmfs setup to fail even though there might be valid cvmfsexec distributions from a previous reconfig/upgrade of the factory since the directory is not visible to the factory (tested this for mode 2 of cvmfsexec only).