I’ve successfully logged into the RSP and started a JupyterHub notebook instance many times. This morning I see that while I’m logged in to https://data.lsst.cloud/ (identity authenticated with GitHub), I’m getting the error: “401 : Unauthorized; User is not authenticated” when I try to start a notebook instance. Is anyone else having this issue or is it just me?
You’re right. we’re investigating.
Hello, I’m facing the exact same issue.
Okay so I am very sorry about this. During Patch Thursday we released some new work (*) that unexpectedly messed with users who already had running notebook sessions. We typically don’t terminate notebook sessions during Patch to reduce disruption to the users, but looks like we should have done this time.
We are now terminating the sessions of affected users. I will update this ticket when this is done. Should only be a few more minutes.
(*) specifically, the change was some improved isolation between user sessions, which now means in your URL bar you see https://frossie.nb.data.lsst.cloud (or whatever your username is) when using the Notebook Aspect. This should have been a transparent change but apparently there’s something going on that we didn’t catch in testing affecting sessions active during the change.
Okay affected users should now be able to return to data.lsst.cloud and start new notebook sessions. I am really sorry for the trouble. Please report back if you still have issues.
Yep, it works now! Thanks for the extremely fast fix and for the status updates along the way.
1 Like
Least we can do.
For the technically curious, since our monitoring system launches new session every time (so we can catch problems for users who are not already working, which are more likely) in this particular case it worked against us, as the fresh sessions by the monitoring bots were not subject to this particular (one-off) migration issue. Which is why y’all noticed before we did, which is most definitely not the goal. Sorry again.
1 Like