You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the role from a control node on to a remote node, in this case the remote node being a Monterey parallels VM hosted on the control node, the ansible execution log (ansible-playbook -vvv) shows the ssh command that gets executed on the control node and just stays there. Nothing happens after that. When I copy this ssh command and run it in another terminal, it takes me to the license agreement page. This stall also seems to stall any other ansible-playbook run after the initial stall. It seems to have something to do with the TTY. The only thing that resolves this and allows further playbook execution on the remote node is ssh-ing into the remote node and manually accepting the license. However, running the playbook locally does work.
The text was updated successfully, but these errors were encountered:
When running the role from a control node on to a remote node, in this case the remote node being a Monterey parallels VM hosted on the control node, the ansible execution log (ansible-playbook -vvv) shows the ssh command that gets executed on the control node and just stays there. Nothing happens after that. When I copy this ssh command and run it in another terminal, it takes me to the license agreement page. This stall also seems to stall any other ansible-playbook run after the initial stall. It seems to have something to do with the TTY. The only thing that resolves this and allows further playbook execution on the remote node is ssh-ing into the remote node and manually accepting the license. However, running the playbook locally does work.
The text was updated successfully, but these errors were encountered: