-
I'm in the process of working through a simple "One managed node, same node as control node" scenario (as specified in the "getting started" documentation) and appear to have stalled out. Specifically, executing the deploy command as follows: sb deploy -f local.ini -i superbench/superbench:v0.4.0-rocm4.2-pytorch1.7 will initiate a series of tasks, culminating with |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Not an issue with a remote managed node; in this context deploy will progress as anticipated. |
Beta Was this translation helpful? Give feedback.
-
Hi, could you try the following command to check Ansible debug log? ANSIBLE_VERBOSITY=4 sb deploy -l localhost -i superbench/superbench:v0.4.0-rocm4.2-pytorch1.7
Because |
Beta Was this translation helpful? Give feedback.
Hi, could you try the following command to check Ansible debug log?
-l localhost
should do the same aslocal.ini
,ANSIBLE_VERBOSITY=4
will tell which command Ansible is actually running.Because
TASK [Copying Context]
is the first task that requiressudo
insb deploy
, could you also verify command likesudo ls
works fine in the local account? If it requires password, pls try withsb deploy -l localhost --host-password [sudo pass] ...
, although in my environment Ansible always prints error message instead of stuck in this case.