Description of problem:

Follow up while investigating RHODS-5211

When an admin users spawns a server for another user, the admin's PVC gets attached to the server (rather than the user's PVC).

This means that when the user logs into RHODS, they will reach their server environment with full access to all data stored in the Admin's PVC.
Furthermore, if the user works in the server, then stops it and starts it again, they won't find any of the work they've done since it will be stored in the admin's PVC rather than their PVC.
If the admin starts more than one server for more than one users, they will all be attached to the same PVC (the admin's). This can lead to conflicts when working on / editing the same files, meaning work can be lost (albeit small portions of it in theory, since JL autosaves every couple of minutes).

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

latest 1.16 RC

Steps to Reproduce

1. Install rhods
2. log in as admin
3. spawn server for another user
4. check server pod, volume attached will be admin's PVC

Actual results:

the admin's PVC gets attached to the server(s) spawned for other users

Expected results:

the PVC of the user for whom the server is being spawned gets attached to the server. This is also necessary to enable the admin user to eventually back up data through the JL interface by accessing the user's PVC.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Latest 1.16 RC

Workaround:

Additional info: