-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bind all files/paths needed for host condor config #36
base: main
Are you sure you want to change the base?
Conversation
The issue mentioned in #21 (comment) ( |
One approach to solve the |
…fig. it disables use of the local config file specified by /usr/local/bin/cmslpc-local-conf.py; cmslpc-local-conf still runs, but the attribute it adds (location of local config file) will now be ignored by condor. this avoids "ERROR: Can't read config source" from condor commands (because the /storage area has wrong ownership inside the container) the local config file is not actually created until the custom /usr/local/bin/condor_submit is used, and it is never used here.
Everything seems to work now, after figuring out how to prevent Condor from reading the non-existent, non-accessible local config file. This does require the "fake python3" approach noted above, because |
Notably, the condor executables built into the coffea-dask image should work in general now (with the usual caveats that the lpc setup requires specifying the schedd or other weird arguments, depending on the command). |
While thinking about how to generalize this beyond the coffea containers, I figured out a simplification that avoids the need for the fake |
It is actually possible to golf this even further as shown at https://github.com/FNALLPC/lpc-scripts/blob/ff047ce7da1965caea1a3b92342346441d6fdda5/bind_condor.sh#L9-L12, but I don't think that's necessary here since some other temporary/hidden files are already created, so one more does not make a big difference. |
This will improve resiliency to minor changes in the LPC condor configuration. (Major changes, e.g. new/different files or paths, would still require a manual update.)