Closed jstrube closed 10 years ago
I could not reproduce the issue with another SRM storage:
[chaen@lxplus0003 ~]$ dirac-dms-add-file /lhcb/user/c/chaen/nonOrigName.txt origName.txt CERN-USER Could not obtain GUID from file through Gaudi, using standard DIRAC method Uploading origName.txt as /lhcb/user/c/chaen/nonOrigName.txt Successfully uploaded origName.txt to CERN-USER (10.4 seconds)
Can this be closed?
Please feel free to mark as "Could not reproduce" or similar and close the issue. I will re-open if this becomes a problem again. Thank you.
I'm trying to upload some files to the grid, but a simple test fails:
dirac-dms-add-file /ilc/user/j/jstrube/Garbage/test.py singleParticles.py CERN-SRM Uploading /ilc/user/j/jstrube/Garbage/test.py __putFile: Failed to put file to storage. srm://srm-public.cern.ch:8443/srm/managerv2?SFN=/castor/cern.ch/grid/ilc/user/j/jstrube/Garbage/test.py: Invalid argument
putAndRegister: Failed to put file to Storage Element. singleParticles.py: __putFile: Failed to put file to storage. Error: failed to upload /ilc/user/j/jstrube/Garbage/test.py to CERN-SRM
On the other hand, naming the remote file and the local file the same succeeds. dirac-dms-add-file /ilc/user/j/jstrube/Garbage/singleParticles.py singleParticles.py CERN-SRM
Uploading /ilc/user/j/jstrube/Garbage/singleParticles.py Successfully uploaded file to CERN-SRM
This is at best unexpected behavior. If the remote and local file are known to be restricted to the same basename, this should be caught at the beginning of the script with an error message. I fail to see, however, why this restriction exists at all.