Thanks for writing in! I tried to clone this workspace myself and was unable to replicate the issue you're having here. To confirm, you're just trying to clone the workspace and not move any of the data in it to another location correct? Also, can you confirm the user account that you're using to clone this workspace?
Thanks for the reply! I took a look at the workspace's Google Project, and as it turns out, the project had filled it's quota for new accounts. I have put in a request for Google increase this quota. You should be able to clone the workspace after that change as been made. I'll let you know once I have any updates.
I don't understand -- there's a limit to how many users can access a particular Google Project? This is extra weird because I've cloned this workspace before, though years ago.
Thanks for reply! There is a limit on how many service accounts can access a Google Project. It's normally not an issue with most workspaces. I did check and the quota for this workspace has been increased. Could you please try cloning the workspace again.
Thanks for letting me know! I've already opened a request for our engineering teams to take a look at the workspace see if they can determine the problem. I'll let you know once I have any updates.
I wanted to give you an update on this request: we took a look at your account and as it turned out, the workspace's pet service accounts didn't get added to your account's proxy group as they should have. We have added them, so please try to clone the workspace again and let us know how it goes.
One note: it may take a few hours for the changes we made to sync in the system, so if you still get the error, please wait a few hours and try again. If you're still getting the error after that, please let us know.
Comments
8 comments
Hi Laura,
Thanks for writing in! I tried to clone this workspace myself and was unable to replicate the issue you're having here. To confirm, you're just trying to clone the workspace and not move any of the data in it to another location correct? Also, can you confirm the user account that you're using to clone this workspace?
Please let me know if you have any questions.
Best,
Josh
It's still happening to me.
I'm just clicking on the clone option under the kebab menu in the upper right. I'm logged in as gauthier@broadinstitute.org and trying to access https://app.terra.bio/#workspaces/anvil-datastorage/1000G-high-coverage-2019
Hi Laura,
Thanks for the reply! I took a look at the workspace's Google Project, and as it turns out, the project had filled it's quota for new accounts. I have put in a request for Google increase this quota. You should be able to clone the workspace after that change as been made. I'll let you know once I have any updates.
Please let me know if you have any questions.
Best,
Josh
I don't understand -- there's a limit to how many users can access a particular Google Project? This is extra weird because I've cloned this workspace before, though years ago.
Hi Laura,
Thanks for reply! There is a limit on how many service accounts can access a Google Project. It's normally not an issue with most workspaces. I did check and the quota for this workspace has been increased. Could you please try cloning the workspace again.
Best,
Josh
Still not working
Hi Laura,
Thanks for letting me know! I've already opened a request for our engineering teams to take a look at the workspace see if they can determine the problem. I'll let you know once I have any updates.
Please let me know if you have any questions.
Best,
Josh
Hi Laura,
I wanted to give you an update on this request: we took a look at your account and as it turned out, the workspace's pet service accounts didn't get added to your account's proxy group as they should have. We have added them, so please try to clone the workspace again and let us know how it goes.
One note: it may take a few hours for the changes we made to sync in the system, so if you still get the error, please wait a few hours and try again. If you're still getting the error after that, please let us know.
Best,
Josh
Please sign in to leave a comment.