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
If it's a minimal Debian install not provisioned using DebOps Preseed/LXC scripts, you should use the bootstrap.yml playbook to prepare the host for use by Ansible. Run this first:
debops bootstrap -l <hostname> -u root -k
This will connect to the root@<hostname> account, install sudo and prepare a management account if you don't already have it. After that, main playbook should work as normal.
Le 7 juil. 2015 à 21:51, Maciej Delmanowski [email protected] a écrit :
If it's a minimal Debian install not provisioned using DebOps Preseed/LXC scripts, you should use the bootstrap.yml playbook to prepare the host for use by Ansible. Run this first:
debops bootstrap -l -u root -k
This will connect to the root@ account, install sudo and prepare a management account if you don't already have it. After that, main playbook should work as normal.
Thank you for the information.
I found it on an another part of the documentation.
I think the « Getting start » section of the web site is missing the bootstrap part.
I will check tomorrow.
JG
I have install a debops environment on my MacBook Air.
I try to setup a host under a minimal Debian Jessie.
MacBookAir jg $ debops
Running Ansible playbook from:
/Users/jg/Library/Application Support/debops/debops-playbooks/playbooks/site.yml ...
PLAY [Gather default and custom facts] ****************************************
GATHERING FACTS ***************************************************************
ok: [myhost.mydomain.local]
TASK: [Check IP address of Ansible Controller] ********************************
ok: [myhost.mydomain.local]
PLAY [Prepare base environment] ***********************************************
TASK: [Create root directories] ***********************************************
failed: [myhost.mydomain.local] => (item={'path': '/etc/ansible/facts.d', 'fact': 'facts'}) => {"failed": true, "item": {"fact": "facts", "path": "/etc/ansible/facts.d"}, "parsed": false}
/bin/sh: sudo: command not found
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/jg/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: auto-mux: Trying existing master
debug1: mux_client_request_session: master session id: 2
Shared connection to xxx.xxx.xxx.xxx closed.
The text was updated successfully, but these errors were encountered: