Hi Lukas, This isn't the intended behaviour: it's the fallback if looking up the PFN fails for any reason (it also doesn't log any extra details when this happens). We'll investigate and get back to you, although it may take a day or two to track it down. Regards, Simon On Wed, Nov 25, 2020 at 12:57:42PM +0000, Lukas Koch wrote:
******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hello all,
It seems like the API does no longer report the replicas of files as it used to.
When I do:
from DIRAC.Resources.Catalog.FileCatalog import FileCatalog self.fc = FileCatalog() rep = self.fc.getReplicas(lurl)
I get:
{'OK': True, 'Value': {'Successful': {'/t2k.org/test/t2kdm/test1.txt': {'CA-SFU-T21-disk': '/t2k.org/test/t2kdm/test1.txt', 'UKI-NORTHGRID-MAN-HEP-disk': '/t2k.org/test/t2kdm/test1.txt', 'UKI-LT2-QMUL2-disk': '/t2k.org/test/t2kdm/test1.txt', 'UKI-SOUTHGRID-RALPP-disk': '/t2k.org/test/t2kdm/test1.txt', 'RAL-LCG2-T2K-tape': '/t2k.org/test/t2kdm/test1.txt'}}, 'Failed': {}}}
The reply does not contain the actual replicas (i.e. the physical locations), but just the catalogue file names. It used to report the actual physical file paths, and now all our scripts are broken.
Was this an intentional change, or is this a bug? If it is intentional, how do I get the physical locations, i.e. the URL to the copies on the storage elements?
Cheers Lukas