Error accessing controlled access data that worked fine earlier
I have a few workspaces with controlled access data (ie, tables of DRS URIs from Gen3). Suddenly I cannot run workflows on this data anymore, even though I am running the exact same workflows with the exact same arguments on the exact same data that I did a few days ago.
ErrorReport(rawls,http error calling uri https://us-central1-broad-dsde-prod.cloudfunctions.net/martha_v2,Some(502 Bad Gateway),List(),List(),None)
I am only running this on with two objects with DRS URIs, so this should be unconnected to the scaling problems currently being worked on. Both my DCP Framework and NIH account links are not expired for at least ten more days.
Due to it containing controlled access data I have a Team Calcium authorization domain on it and have not added tech support to the workspace. The problem persists in more than one workspace anyway.
Comments
9 comments
Hi Aisling,
Thanks for flagging this up. Would you be willing to relink your NIH Account and DCP Framework Services just to rule out the possibility of there being a mismatch in permissions setting somewhere along the way?
Kind regards,
Jason
Went to re-verify DCP Framework and got this error. Separately, I got a certificate error yesterday when accessing gen3.datastage.io so I'm wondering if this is a hiccup caused by the move to .gov?
It's very possible. We've just tried relinking ours and found success, so it could have been a blip on Gen3's side. Would you mind trying once again?
I was able to reconnect the DCP framework, but I tested the controlled access data just now and I am still getting this error.
Our engineers are taking a look at errors related to Gen 3/DRS. We recommend holding off for now and I'll let you know as soon as I hear more from them.
Alright, thanks for the update.
Hi Aisling,
Are you currently using app.terra.bio for your work or one of the other branded UIs (like AnVIL or SCP)?
Jason
That seems to have done the trick. I was working on the BDC skin. It appears to be working on app.terra.bio.
As a side note, notebooks do not work at all on the BDC skin -- they show up fine, but when trying to edit them the UI never loads even after the notebook runtime has fired up and after refreshing the page a few times. They still work on app.terra.bio thankfully.
Thanks for letting us know that it doesn't work in BDC but does work in app.terra.bio. Thank you too for flagging up the notebook issue—I will be sure to get the right eyes on that.
We have someone working on the issue who is a member of the Team Calcium auth domain. As such, can you share the workspace with them (mbaumann@broadinstitute.org) so they can take a closer look at this?
Please sign in to leave a comment.