Closed amaltaro closed 2 years ago
Alan, this has nothing to do with dbs2go codebase since you're still using Python DBSWriter on testbed, see
# type of DBSWriter
scurl https://cmsweb-testbed.cern.ch/dbs/int/global/DBSWriter/serverinfo
{"dbs_instance": "int/global", "dbs_version": "3.16.0-comp5"}
# type of DBSReader
scurl https://cmsweb-testbed.cern.ch/dbs/int/global/DBSReader/serverinfo
[{"dbs_version":"v00.04.57","server":"dbs2go git=v00.04.57 go=go1.17.7 date=2022-16-03"}]
So, the DBSWriter is still python code, while only DBSReader is new server. I will close this issue and you need to open corresponding ticket (if any) on DBS python codebase. I think the issue should go to DBSClient rather the server.
Oh, you are correct! Apologies for the noise Valentin. I won't even bother creating such issue for python-based DBS. Thanks
While running standard integration tests with a pre-production WMAgent node - which points to DBS Int (cmsweb-testbed), I found this exception in the DBS3Upload component:
The error itself looks Okay to me, since we tried to insert first a DQMIO data/datatier, when we should have injected first the AOD one.
The actual problem reported in this issue is:
Perhaps the best would be to report back to the client something like:
where BLAH is the parent name. Or perhaps something like: "Parent for dataset: BLAH has not been inserted yet.". Or any message that is more clear on what the actual error is.