Dots seem to cause problems in entry names
Steve Timm noticed problems when using entry names like:
"FNAL_HEPCLOUD_AWS_us-east-1a_m3.2xlarge", including a dot.
They "have seen some stuff that was unhappy because of this".
The goal of this ticket is to:
- verify what is the problem and why
- solve it if it is easy (to allow dots in the names)
- otherwise document that entry names cannot include dots (list the valid characters for entry names)
#4 Updated by Leonardo Lai over 1 year ago
The following is an observation that is not directly related to the "." bug, but has something to do with prohibited characters in entry names.
In GlideinWMS there are some directories named like the corresponding entries, e.g. inside the factory submit directory. There are entry-like directories also in one of the branches I'm currently developing (not released yet).
The entry names become part of a path string when you refer the files contained in them.
Issues may arise when such files should be transferred by Condor via condor_submit, if the path contains symbols that HTCondor does not support.
One of these is the percentage ("%"), which produces a weird error (Globus 135: job manager could not stage file) if ever a file having "%" in its name (or path) is transferred using the 'transfer_input_file' option of condor_submit.
This is likely due to the fact that HTCondor internally uses the "%" symbol for macros, although undocumented.
Therefore I propose to add "%" to the list of prohibited characters in an entry name, and document it somewhere, together with the symbol "." until we find a fix.