-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: provision VM + ansible #2634
Comments
I don't think the use of localhost is the problem here. The VM spawned by The error message also suggests a different cause: I'm seeing |
How about making a proper inventory file with |
Also possible, sure. It might be possible to create it once for each guest and re-use it, it's probably read-only from that point anyway. |
The
|
Probably it is worth putting in |
Can you run it with more verbose Ansible, |
|
I for one would stay away from anything system-wide. tmt usually talks to one guest when running |
Ah, yes, definitely in the plan. Re-use by all invocations of |
@praiskup hm, no idea, maybe the server log would help. And maybe SSH is not kidding when it complains about an invalid SSH version... |
Note that we enforce The |
And, now I noticed I had ~/.ansible.cfg :
Commenting that out also helped. I don't remember the reasons for this... |
Yes, that does not seem right, it's definitely sending mixed signals to Ansible.
Would |
Yes, it works without
These warnings don't seem to be candidates for ignoring :-/ though
|
These warnings appear no matter if I use |
What helps is to move |
From Fedora CI: https://matrix.to/#/!cfWVeczGVJbiKSlrwi:fedoraproject.org/$pWT2oRW18ucYgnv6-Yyqfbx-9M6UJdLtF1-3lLM1T8A?via=fedoraproject.org&via=fedora.im&via=matrix.org.
It seems when
provision --how virtual
, and there is aprepare --how ansible
step, then theansible-playbook
command is run on the host, and not within the virtual machine. That would be fine, except it is using-i root@localhost
The text was updated successfully, but these errors were encountered: