I am having problems with vagrant vmware provider not copying the salt
minion config file from the host to the vagrant dev vm and subsequent salt
configuration is not running correctly as a default minion file provided in
the box is not being relpaced.
The minion file is specified in the Vagrantfile and I can see it being
copied to /tmp on the vm but it is not being moved /etc/salt/minion for
salt to use it.
Any idea what would be preventing it from being copied there?
Here's the relevant section vagrantfiile, I've turn off running
salt.run_highstate and tried both with salt.no_minion true/false
config.vm.provision :salt do |salt|
salt.minion_config = "salt-config/tv-dev-vmware/minion-vagrant"
salt.run_highstate = false
# salt.no_minion = false # Already installed by packer
end
Here's the trace of vagrant debug log showing it being copied to the vm but
I can't find anything which should be moving it to /etc
INFO environment: Running hook: provisioner_run
INFO runner: Running action: #<Method:
Vagrant::Action::Builtin::Provision#run_provisioner>
INFO warden: Calling IN action:
#<Proc:0x3627ac8@C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:94
(lambda)>
INFO interface: info: Copying salt minion config to vm.
Copying salt minion config to vm.
DEBUG ssh: Uploading:
C:/recon/tv/tvplatform/salt-config/tv-dev-vmware/minion-vagrant to
/tmp/minion
DEBUG ssh: Re-using SSH connection.
INFO interface: info: Checking if salt-minion is installed
Checking if salt-minion is installed
So when salt runts the wrong minion config is used.
My set up:
vagrant 1.4.3
vagrant-vmware-workstation 2.3.1
vmware workstation 10.0.1 build -1379776
Windows 7
Adrian
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
