Hello, Trying to figure out why Vagrant (tried 1.5.1, 1.5.2 and 1.5.3) would run the same provisioners multiple times on "up" and "destroy".
Here is the output from a "destroy": $ vagrant destroy --force WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.9.1 ==> default: Terminating the instance... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'salt' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'salt' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'salt' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'salt' provisioner... I have two shell provisioners and one salt. You can see it is running them four times. My guess I I have a problem with my Vagrantfile? Any ideas on what to look for? Would a copy of my Vagrantfile help? FWIW, I am using AWS as the provider. Thanks, Steve. -- 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/d/optout.
