Closed ryanlovett closed 5 years ago
@papajohn @simon-mo git-sync should start user servers if they are not already running. I do recall however that if the user doesn't exist yet on the hub then they might run into this. I'll need to double-check. In the interim I'm going to manually create the users based on the SIS roster.
My user definitely existed already when I had this problem.
On Wed, Jan 23, 2019 at 9:43 AM Ryan Lovett notifications@github.com wrote:
@papajohn https://github.com/papajohn @simon-mo https://github.com/simon-mo git-sync should start user servers if they are not already running. I do recall however that if the user doesn't exist yet on the hub then they might run into this. I'll need to double-check. In the interim I'm going to manually create the users based on the SIS roster.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/berkeley-dsep-infra/data100-19s/issues/34#issuecomment-456897764, or mute the thread https://github.com/notifications/unsubscribe-auth/AATikYudlrDqCfgYv1o2lY9CO91-ptA7ks5vGJ8qgaJpZM4aPSYC .
Adding a data point, when I visit
as a hub admin, the user server starts and git-sync operates normally.
I'm going to try user-redirect/git-sync as a user who has never logged in.
I was unable to reproduce as the new user "courses-stat". I'm thinking that this isn't a git-sync issue.
Can you please slack me the name of users with "service unavailable" ?
Edit: I'm checking the users in the piazza post.
I believe the cause of this is fixed by #35.
We upscaled the cluster on Monday, but the singleuser environment wasn't automatically pulled onto the node. When user servers were started on these new nodes, dockerd had to fetch the image from docker hub and some users timed out while the transfer was underway.
@papajohn emailed: