[Workbench] Make note of lag time when changing git permissions
I created a new git repo bcosc.gatk2 using the admin account for firstname.lastname@example.org, which has manage access.
git clone email@example.com:bcosc.gatk2.git
Cloning into 'bcosc.gatk2'...
R access for bcosc.gatk2 DENIED to qr1hi-tpzed-rv6f0l8lbvdzkog
(Or there may be no repository at the given path. Did you spell it correctly?)
fatal: The remote end hung up unexpectedly
Then I just granted them owner access and the git clone worked.
#1 Updated by Brett Smith over 5 years ago
- Target version set to Bug Triage
Can you please clarify what you mean when you say you "granted them owner access?" If you created the repository with your BU account, I believe it would've been owned by that same user from the time it was created.
How quickly did all this happen? It can take a minute or so for changes to git repositories in Arvados to be reflected on the git server. Like the error message indicates, it's possible that the repository simply didn't exist when you first tried to clone it. Is that a reasonable possibility?
#4 Updated by Peter Amstutz over 5 years ago
- Subject changed from Creating a new git repo and granting manage access denied a git clone to [Workbench] Make note of lag time when changing git permissions
- Status changed from Feedback to In Progress
Updating this story to add a note to Workbench that there is a lag time on updating git permissions.
#6 Updated by Brett Smith over 5 years ago