Describe the bug
When a vagrant developer machine runs refresh_vagrant_workers.py the running workers are not connected to the developer machine with ssh.
Expected behavior
when refresh_vagrant_workers is ran, it should connect to all workers and store them in a JSON file (config/autograding_workers.json) verifying that they are connected. When swapping to the submitty daemon (sudo su submitty_daemon) you should be able to run ssh worker-1 (or 2.. 3 .. etc) and shell into the worker machine.
To Reproduce
Steps to reproduce the behavior:
- create a vagrant worker (
vagrant workers generate, vagrant workers up)
- ssh into development vagrant machine (
vagrant ssh)
- run
refresh_vagrant_workers in any directory
- See error
Configuration
- OS: Arch Linux
- Browser N/A
Screenshots
Additional context
Describe the bug
When a vagrant developer machine runs
refresh_vagrant_workers.pythe running workers are not connected to the developer machine with ssh.Expected behavior
when
refresh_vagrant_workersis ran, it should connect to all workers and store them in a JSON file (config/autograding_workers.json) verifying that they are connected. When swapping to the submitty daemon (sudo su submitty_daemon) you should be able to runssh worker-1 (or 2.. 3 .. etc)and shell into the worker machine.To Reproduce
Steps to reproduce the behavior:
vagrant workers generate, vagrant workers up)vagrant ssh)refresh_vagrant_workersin any directoryConfiguration
Screenshots
Additional context