Description of problem:

When a RHODS admin user tried to stop all the servers or a specific server from Administration tab of Spawner nothing really happens: the notebook servers remain running.

The only way for and admin to stop a server owned by other user is to click on "view server" which redirects the admin to "Notebook Server Control Panel" where the button "stop notebook server" works as expected.

Prerequisites (if any, like setup, operators/versions):

RHODS installed

RHODS group configuration set up

Steps to Reproduce

1. Spawn a notebook using a basic rhods userA
2. Access dashboard with a rhods admin userB
3. go to Jupyter Spawner > Administration tab
4. search for the running notebook owned by userA
5. click on 3-dots menu > stop server action
6. check what happens: is the notebook stopped?
7. click on "stop all servers" button 
8. check what happens: is the notebook stopped?
9. click on "view server" link
10. click on "stop notebook server" button
11. check what happens: is the notebook stopped?

Actual results:

RHODS admins cannot stop notebook using "Stop all servers" and "stop server" buttons in Spawner UI > Administration tab

Expected results:

RHODS admin can stop notebooks owned by other users in any of the following way:

• clicking on "stop all servers" button
• clicking on 3-dot menu > stop server action
• clicking on "view server" link and then "stop notebook server" in the NB Control Panel

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

quay.io/cfchase/rhods-operator-live-catalog:1.20.0-rc4

quay.io/cfchase/rhods-operator-live-catalog:1.20.0-rc2

Workaround:

clicking on "view server" link and then "stop notebook server" in the NB Control Panel

Additional info: