使用ansible_local预配器无法在多个来宾计算机上使用流浪汉运行剧本

时间:2020-09-09 17:46:34

标签: ansible windows-10 vagrant virtualbox vagrant-provision

我已经在'Windows 10'机器上安装了vagrant,并使用vagrantfile在Virtual Box上创建了2个guest虚拟机以在其上运行Ansible剧本。 Vagrant同时创建了两个来宾计算机,但playbook仅在Controller节点上运行,即它在Controller节点上安装了Ansible和playbook中提到的其他软件包,但未在第二个guest计算机上安装。我也需要在第二台计算机上安装其他软件包,但是由于错误而失败- fatal: [centos4]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '172.28.128.20' (ECDSA) to the list of known hosts.\r\nno such identity: /vagrant/.vagrant/machines/centos4/virtualbox/private_key: No such file or directory\r\nPermission denied (publickey,gssapi-keyex,gssapi-with-mic).", "unreachable": true}

两台机器都被创建,我可以看到Windows文件夹'F:\ vagrant ansible.vagrant \ machines \ centos4 \ virtualbox'中存在private_key文件。有人可以帮助您解决此问题吗?

我在同一个文件夹中都有一个Ansible配置文件,清单,剧本和Vagrantfile。


ansible.cfg file -

# uncomment this to disable SSH key host checking
host_key_checking = False

[privilege_escalation]
become=True
become_method=sudo
become_user=root
become_ask_pass=False

[ssh_connection]

# ssh arguments to use
ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes

-----------------------------------------------------------------------------------
invetory file - 

centos3 ansible_connection=local

centos4 ansible_host=172.28.128.20 ansible_ssh_private_key_file=/vagrant/.vagrant/machines/centos4/virtualbox/private_key

[nodes]

centos[3:4]

----------------------------------------------------------------------------------
---
- hosts: all
  gather_facts: false
  
  tasks: 
  - name: Install nmap package
    yum:
     name: nmap
     state: installed
--------------------------------------------------------------------------------------
Vagrantfile - 

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

    config.vm.box = "centos/7"

    config.vm.define "centos4" do |c2|

    c2.vm.hostname = 'ansiblecentos4'
    
    c2.vm.network :private_network, ip: "172.28.128.20"

    c2.vm.provider :virtualbox do |v2|
      
      v2.name = "AnsibleCentos4"
      
      v2.memory = "512"
    
    end

end

  config.vm.define "centos3" do |c1|
    
    c1.vm.hostname = 'ansiblecontrollercentos3'
    
    c1.vm.network :private_network, ip: "172.28.128.10"

    c1.vm.provision :ansible_local do |ansible|
      
      ansible.playbook       = "playbook.yml"
      ansible.verbose        = true
      ansible.install        = true
      ansible.limit          = "all" 
      ansible.inventory_path = "inventory"
      ansible.config_file    = "ansible.cfg"
    end
    
    c1.vm.provider :virtualbox do |v1|
      v1.name = "AnsibleCentos3"
      v1.memory = "512"
     end
   end  
end

Below are the details:- 

Host machine - Windows 10 Home single language

Vagrant version - Vagrant 2.2.10

Virtual Box - 6.1

似乎ansible控制器节点无法通过基于密钥的登录连接到ansible受管节点。 花了几天的时间之后,我看到来宾计算机上的/ vagrant中没有主机的'.vagrant'文件夹。我可以在来宾计算机上的/ vagrant中看到所有其他文件,例如playbook.yml,Vagrantfile,ansible.cfg,但看不到.vagrant文​​件夹,我认为这是错误提及它的原因'......没有此类文件或目录'。 似乎sync文件夹实际上不同步文件/文件夹。是因为我们将行“ config.vm.synced_folder”放在vagrantfile中的位置吗? 我还曾在ansible.cfg中提到过“ host_key_checking = False”,但仍然提到了有关private_key的错误。

有什么想法为什么会发生以及如何解决?

还有如何建立一个无所事事的环境?是#vagrant up是正确的还是#vagrant up --provision。到目前为止,我一直在使用#vagrant,并且遇到上述问题。

0 个答案:

没有答案
相关问题