Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with vagrant up --provider=aws #11371

Closed
nickpwhite opened this issue Feb 3, 2020 · 2 comments
Closed

Error with vagrant up --provider=aws #11371

nickpwhite opened this issue Feb 3, 2020 · 2 comments

Comments

@nickpwhite
Copy link

nickpwhite commented Feb 3, 2020

Vagrant version

$ vagrant --version
Vagrant 2.2.7

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

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

Vagrant.configure("2") do |config|
  config.vm.box = "dummy"

  config.vm.provider :aws do |aws, override|
    aws.ami = "ami-2f15061f"
    aws.aws_profile = ENV["AWS_PROFILE"]

    override.ssh.username = "ubuntu"
    override.ssh.private_key_path = "~/.ssh/id_rsa"
  end
end

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

  1. Install the vagrant-aws plugin vagrant plugin install vagrant-aws
  2. Add the dummy box for vagrant-aws vagrant box add dummy https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
  3. Using the provided Vagrantfile, bring up the machine vagrant up --provider=aws
@chrisroberts
Copy link
Member

Hi there. Please see mitchellh/vagrant-aws#566 for more information. Cheers!

@ghost
Copy link

ghost commented Mar 5, 2020

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 ghost locked and limited conversation to collaborators Mar 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants