esgf2-us/metagrid

Globus transfer task failed: Your request to the Globus transfer service was invalid. Please contact support.

Closed this issue · 8 comments

yzhang-aos commented

I was able to sign in to Globus and specify an end point, but I can't proceed any further and got the error message that "Globus transfer task failed: Your request to the Globus transfer service was invalid. Please contact support."

sashakames commented

Thank you for reporting. Our experience has shown that there might be an issue with the destination endpoint. We will look into supplying specific error codes so we can trace your error in our logs.

wilbertw commented

@sashakames I have exactly the same problem when I try to transfer files to Perlmutter, and it has prevented me from using Globus for transferring any data since the Globus option was disabled from the original ESGF website. Has there been any progress on this? Thanks!

yzhang-aos commented
sashakames commented

@wilbertw @yzhang-aos We can see if there are failed transfers on the aims2 container logs. If not, please try our alternate testing site https://esgf-dev1.llnl.gov/ Ping me on my @llnl.gov email when you do and I'll check that log. The feature to provide a error ID is forthcoming.

If you can do a test transfer to a Globus Connect Personal in the meantime with fx fields, that could help determine if the issue is at NERSC.

sashakames commented

@downiec @sturoscy-personal Lets use this issue to track the solution if that makes sense. We need to update the tokens after we receive the target endpoint info. This will be more complicated if we need to add source endpoints too.

sashakames commented

Update: The proof-of-concept test works with "NERSC Perlmutter" but will not with other destination endpoint/collections. https://esgf-dev1.llnl.gov/
Next up we need a comprehensive solution that supports additional managed endpoints.

sashakames commented

More on the Scopes issue we are not done yet:

Sasha,

7399956e-a57b-4560-b3d7-a035ff42cad4 is NCCS Open DTN (Globus 5) which is a high assurance GCS mapped collection. High assurance GCS mapped collections do not have a data_access scope as their polices already cover the ability for users to revoke access by ending their current session.

Whatever code is requesting the scope should check if the mapped collection is high assurance, and if so skip the dependent data access consent.

Hope that helps,
Aaron

sashakames commented

Going to open a new issue instead..