go to the class formgrader service page (example.com/services/test)
. Click on Manage Assignments
Jupyterhub log:
service name: test
service user: grader-test
... JupyterHub log:191] 404 GET /hub/api/users/grader-test ...
... ServerApp] Error: Not able to get Jupyterhub user: {authenticated_user}
... ServerApp] Make sure you start your service with a valid admin_user 'api_token' in your Jupyterhub config
... ServerApp] Uncaught exception GET /services/test/formgrader
...
nbgrader.auth.jupyterhub.JupyterhubApiError: JupyterhubAPI returned a status code of: 404 for api_path: /users/grader-test
ServerApp] 500 GET /services/test/formgrader
Browser request log
also shows a 500
Adding the service user (which already exists in /etc/passwd) using the admin panel solves the issue.
Why does the service user has to exist in Jupyterhub's database? Is this a bug or feature?
Operating system
ArchLinux
nbgrader --version
0.9.2
jupyterhub --version
(if used with JupyterHub)4.0.2
jupyter notebook --version
7.1.2
Expected behavior
Formgrader page does not show an error.
Actual behavior
Steps to reproduce the behavior
PAMAuthenticator
SystemdSpawner
(I believe this is unrelated)example.com/services/test
)Manage Assignments
Jupyterhub log:
test
grader-test
Browser request log
also shows a 500
Adding the service user (which already exists in
/etc/passwd
) using the admin panel solves the issue.Why does the service user has to exist in Jupyterhub's database? Is this a bug or feature?