Permission error to access-granted files

Data Access
1

Hello AnVIL team,

I hope you’re doing well. I’m currently having trouble accessing a controlled dataset (phs003047; GREGoR) for which I have been granted access to.

I followed instructions found on the forum and made sure I that I have:

  • an AnVIL/Terra account with CADR-compliant institution email,
  • approval to access the dataset through dbGaP (dbgap_phs003047_c1 and dbgap_phs003047_c2),
  • a working billing project in Terra (shared with me by my PI),
  • an eRA commons ID linked to Login.gov,
  • a linked NIH RAS identity in Terra under “Profile” > “External Identities”,
  • a membership to the appropriate group under “Groups”

I also tried unlinking and relinking the RAS identity multiple times and waited at least 24 hours. However, whenever I run a WDL workflow, I keep getting an “AccessDenied” error message in the GCP Batch Job log, which looks like the following (shortened version and actual paths masked):

ERROR:getm.cli:{"message": "url innaccessable", "text": "<?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>pet-xx@xx.iam.gserviceaccount.com does not have storage.objects.get access to the Google Cloud Storage object. Permission 'storage.objects.get' denied on resource '//storage.googleapis.com/projects/_/buckets/xx.cram' (or it may not exist).</Details></Error>", ... "status_code": 403}

I was really hoping I could get any help or advice in resolving this issue. Please let me know if you need any more information.

Thank you so much!

image
image459×147 11 KB

image
image685×170 8.36 KB

2

Hi @Sang_Yoon_Byun ,

Thanks for this question and for walking through all the troubleshooting steps! Your screenshots suggest you are set up correctly.

This might be due to a recent software bug discovered in DRS/RAS access for GREGoR data. The team is actively reviewing a fix for this, with an expected turnaround of a few days.

Please let us know if this persists in a few days. Apologies for the frustrating issue!

Best,
Ava

1 Like
3

Hi @Sang_Yoon_Byun ,

Just a quick update - the fix is now in production. Can you try running your workflow again?

Thanks!
Ava

1 Like
4

Hi @avahoffman ,

It’s working now! That was really quick :slight_smile:

Thank you so much your help!

1 Like