Open karnold opened 8 years ago
This is probably happening because the aws provider runs provisioner cleanup after the instance has been terminated (at least, as of v0.7.0):
https://github.com/mitchellh/vagrant-aws/blob/v0.7.0/lib/vagrant-aws/action.rb#L56
If the chef cleanup routine is trying to read state from the agent, then it's out of luck because everything is gone at this point.
In contrast, core vagrant switched to running cleanup actions for VirtualBox et. al. before termination in v1.8.0:
https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#180-december-21-2015
This also appears to be when the Chef provisioner was changed to read state from the agent.
Looks like PR #452 may address this.
I can successfully run vagrant up and vagrant provision on a machine with no issue. However when I run vagrant down I get the following error:
Note that I am provisioning this via amazon AWS. The aws instance is destroyed as expected, however it is not removed from the chef server.
Here is my Vagrantfile: