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
This worked in version 2.2.6 but not in 2.2.7 which is why I've opened the issue here instead of with the vagrant-aws plugin. If it's the case that this is an issue with the plugin I'll open an issue there instead.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Mar 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vagrant version
This worked in version 2.2.6 but not in 2.2.7 which is why I've opened the issue here instead of with the
vagrant-aws
plugin. If it's the case that this is an issue with the plugin I'll open an issue there instead.Host operating system
Observed on both Ubuntu 18.04 and MacOS
Guest operating system
Ubuntu 14.04
Vagrantfile
Debug output
https://gist.github.com/nickpwhite/98e13c65eb5f269db2e0c6e6d3f371b5
Expected behavior
The machine should have been created in EC2.
Actual behavior
There was an exception and the box was not created.
Steps to reproduce
vagrant plugin install vagrant-aws
vagrant box add dummy https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
vagrant up --provider=aws
The text was updated successfully, but these errors were encountered: