by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    dragon788
    @dragon788
    vagrant-aws and vagrant-azure both
    GHApps
    @GHapps
    Hi there - I am on windows and have an rsync problem. Im trying to use cwRsync. When I do a vagrant up and it tries to sync my folder I get either a "The host path of the shared folder is missing" if I try to do a fully qualified cygwin path or a "No such file or directory" if I try to use a relative one. Im using vagrant 1.9.1 and vagrant-aws 0.7.2
    Rahul Nigam
    @Rahulnigam28
    Hello
    I am trying to deploy AWS instances from Vagrant. However, I am unable to ssh to instances as my terminal hangs indefinitely on "Waiting for SSH to become available". I used override.ssh.username = 'ubuntu' initially for deploying AMI image. After changing my username from 'ubuntu' to 'ec2-user' I was able to ssh into my instances. I am running Vagrant from my virtual machine in VMware in bridged mode and can ssh to external internet.
    Why is it now working with any other username. Please help.
    dragon788
    @dragon788
    @Rahulnigam28 did you create the AMI yourself or is it a prebuilt one?
    unless you created the AMI yourself with Packer (https://github.com/mitchellh/packer) you are only going to be able to use the users already provisioned within that AMI
    Rahul Nigam
    @Rahulnigam28
    I used the vagrant box "dummy" for aws and later configured the Vagrant file to create ssh username
    Rahul Nigam
    @Rahulnigam28
    I did not create a new AMI, however if I am doing a override for username wont that create a new default username?
    dragon788
    @dragon788
    @Rahulnigam28 correct, vagrant can run provisioning scripts, but it has to use an existing user to do so, if you need a different user on there you'd need to run a couple scripts to add the user and then change it in your Vagrantfile, which could get pretty hairy and fragile
    @GHapps it appears cwRsync behaves as only a client in the free version, you will probably need the paid version to get the server to run as a service, are you running this specifically with vagrant-aws or just a local vagrant+virtualbox install?
    @iDVB it could be an issue with the embedded version of ruby glitching out, if you kill all copies of vagrant/ruby on your system and try again do you get the same error? also, are you using vagrant-aws or is this for a local machine? you might want the https://gitter.im/mitchellh/vagrant channel for non-AWS issues
    Rahul Nigam
    @Rahulnigam28
    Thank you
    cornfeedhobo
    @cornfeedhobo
    would it be possible to sponsor this plugin becoming part of the core project?
    dragon788
    @dragon788
    though this repo lives under mitchellh's account I think Hashicorp stays fairly busy with the core Vagrant plus their numerous other projects, though I would imagine that you could request a bounty via BountySource or something similar if you need paid support for specific features and their developers or other open sourcerers could assist if they have the time and skills
    cornfeedhobo
    @cornfeedhobo
    Yeah, I am sensitive to their load, hence the mention of money :p
    I guess I just don't see much difference between this and the other providers. Seems like the real limit is ability to hire and pile-o-cash.
    dragon788
    @dragon788
    yeah, like many open source projects, the most activity (bug reports/fixes/new features) happens where the largest number of users and developers that can contribute are concentrated, it seems like for many the aws is "good enough" but I'd also imagine that for larger scale projects they move fairly quickly to Terraform as well
    glennmcclements
    @glennmcclements
    Anyone know if there's a way to use the ami_name instead of ami_id when spinning up a VM (as terraform supports for example hashicorp/terraform#3935)
    Kevin Cormier
    @kcormier
    Hey Guys. I've noticed there is a pretty high number of stale pull requests. We're using vagrant-aws in house and have submitted a pull request around network interfaces (mitchellh/vagrant-aws#512)
    I'm just wondering if anyone can provide some context on how often pull requests get reviewed/get a response or if they really ever get merged back in.
    cornfeedhobo
    @cornfeedhobo
    kcormier: you should email the mailing list about this. word is that otto resources were being reallocated, but its been months ....
    rizaermiser
    @rizaermiser
    hello
    is there anyone here?
    milind sisodiya
    @milind2
    Hi,
    Any one can help me for below issue my.My vagrant execution hang at ssh.Below is snap for it.I have security group which is universally open.
    [root@ip-172-31-18-214 vagrant_test]# vagrant up --provider=aws
    Bringing machine 'default' up with 'aws' provider...
    ==> default: Warning! The AWS provider doesn't support any of the Vagrant
    ==> default: high-level network configurations (config.vm.network). They
    ==> default: will be silently ignored.
    ==> default: Warning! You're launching this instance into a VPC without an
    ==> default: elastic IP. Please verify you're properly connected to a VPN so
    ==> default: you can access this machine, otherwise Vagrant will not be able
    ==> default: to SSH into it.
    ==> default: Launching an instance with the following settings...
    ==> default: -- Type: m3.medium
    ==> default: -- AMI: ami-c998b6b2
    ==> default: -- Region: us-east-1
    ==> default: -- Keypair: guruom_northv
    ==> default: -- Subnet ID: subnet-70d7a338
    ==> default: -- Security Groups: ["sg-25a1b055"]
    ==> default: -- Block Device Mapping: []
    ==> default: -- Terminate On Shutdown: false
    ==> default: -- Monitoring: false
    ==> default: -- EBS optimized: false
    ==> default: -- Source Destination check:
    ==> default: -- Assigning a public IP address in a VPC: true
    ==> default: -- VPC tenancy specification: default
    ==> default: Waiting for instance to become "ready"...
    ==> default: Waiting for SSH to become available...
    3vcloud
    @3vcloud
    1. Make sure your security group has access to your chosen subnet.
    2.
    Make sure your server has ssh access enabled and you have the right ssh key/ usrname and password for whatever instance type you've chosen
    milind sisodiya
    @milind2
    can you please elaborate more I have security group which is universally accessible
    how can i assign security group to subnet.
    milind sisodiya
    @milind2

    I am able to connect to my EC2 Instance via 'ssh' from a Putty installed on window ,
    however, Vagrant can't connect with the same ami, key/pair, and .pem file.

    I have checked my security group is opened.I have attached snapshot for it.

    Vagrant.configure('2') do |config|
    config.vm.box = 'dummy'
    config.vm.box_url = "https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box"
    config.vm.provider :aws do |aws, override|
    aws.access_key_id = 'KIAIETI6RM6RKS6XMEQ'
    aws.secret_access_key = '4C0TIFMBIJs0/DR00aLiJysnUBUeW4pqiYBx2eX/'
    aws.subnet_id = "subnet-8f2205d5"
    aws.region = "us-east-1"
    aws.availability_zone = "us-east-1b"
    aws.associate_public_ip = true
    aws.security_groups = ['sg-d020c2a3'] # Group names if default VPC, group IDs otherwise.
    aws.keypair_name = 'guruommykey'
    aws.region = 'us-east-1'
    aws.instance_type = 't2.micro'
    aws.ami = "ami-c998b6b2"
    override.ssh.username = 'ec2-user'
    override.ssh.private_key_path = 'D:\Users\misisodi\Downloads\guruommykey.pem' # Normally “./ssh/id_rsa”.
    end
    end


    C:\Users\misisodi>vagrant up --provider=aws --debug
    INFO global: Vagrant version: 2.0.0
    INFO global: Ruby version: 2.3.4
    INFO global: RubyGems version: 2.5.2.1
    INFO global: VAGRANT_EXECUTABLE="C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-2.0.0\bin\vagrant"
    INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\HashiCorp\Vagrant\embedded"
    INFO global: VAGRANT_INSTALLER_ENV="1"
    INFO global: VAGRANT_INSTALLER_VERSION="2"
    INFO global: VAGRANT_LOG="debug"
    INFO global: VAGRANT_OLDENV="ExitCode=00000000"
    INFO global: VAGRANT_OLD_ENV_ALLUSERSPROFILE="C:\ProgramData"
    INFO global: VAGRANT_OLD_ENV_APPDATA="C:\Users\misisodi\AppData\Roaming"
    INFO global: VAGRANT_OLD_ENV_ChocolateyInstall="C:\ProgramData\chocolatey"
    INFO global: VAGRANT_OLD_ENV_ChocolateyLastPathUpdate="Thu Jun 22 15:25:07 2017"
    INFO global: VAGRANT_OLD_ENV_CLASSPATH=".;C:\Program Files (x86)\QuickTime\QTSystem\QTJava.zip"
    INFO global: VAGRANT_OLD_ENV_CommonProgramFiles="C:\Program Files\Common Files"
    INFO global: VAGRANT_OLD_ENV_CommonProgramFiles(x86)="C:\Program Files (x86)\Common Files"
    INFO global: VAGRANT_OLD_ENV_CommonProgramW6432="C:\Program Files\Common Files"
    INFO global: VAGRANT_OLD_ENV_COMPUTERNAME="DIN16001396"
    INFO global: VAGRANT_OLD_ENV_ComSpec="C:\WINDOWS\system32\cmd.exe"
    INFO global: VAGRANT_OLD_ENV_FP_NO_HOST_CHECK="NO"
    INFO global: VAGRANT_OLD_ENV_HOMEDRIVE="C:"
    INFO global: VAGRANT_OLD_ENV_HOMEPATH="\Users\misisodi"
    INFO global: VAGRANT_OLD_ENV_LOCALAPPDATA="C:\Users\misisodi\AppData\Local"
    INFO global: VAGRANT_OLD_ENV_LOGONSERVER="\\WADINMUM07"
    INFO global: VAGRANT_OLD_ENV_NUMBER_OF_PROCESSORS="4"
    INFO global: VAGRANT_OLD_ENV_OS="Windows_NT"
    INFO global: VAGRANT_OLD_ENV_Path="C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\
    v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\CapgeminiScripts\Support Tools\;C:\ProgramData\chocolatey\bin
    C:\Program Files\Git\cmd;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Skype\Phone\;C:\HashiCorp\Vagrant
    \bin;C:\Program Files\Amazon\AWSCLI\"
    INFO global: VAGRANT_OLD_ENV_PATHEXT=".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC"
    INFO global: VAGRANT_OLD_ENV_PROCESSOR_ARCHITECTURE="AMD64"
    INFO global: VAGRANT_OLD_ENV_PROCESSOR_IDENTIFIER="Intel64 Family 6 Model 58 Stepping 9, GenuineIntel"
    INFO global: VAGRANT_OLD_ENV_PROCESSOR_LEVEL="6"
    INFO global: VAGRANT_OLD_ENV_PROCESSOR_REVISION="3a09"
    INFO global: VAGRANT_OLD_ENV_ProgramData="C:\ProgramData"
    INFO global: VAGRANT_OLD_ENV_ProgramFiles="C:\Program Files"
    INFO global: VAGRANT_OLD_ENV_ProgramFiles(x86)="C:\Program Files (x86)"
    INFO global: VAGRANT_OLD_ENV_ProgramW6432="C:\Program Files"
    INFO global: VAGRANT_OLD_ENV_PROMPT="$P$G"
    INFO global: VAGRANT_OLD_ENV_PSModulePath="C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\"
    INFO global: VAGRANT_OLD_ENV_PUBLIC=

    3vcloud
    @3vcloud
    Bring the server up without SSH using vagrant up --no-provision --provider=aws
    Then try vagrant ssh --debug to see any other issues
    The only other thing I would try is to assign an elastic IP address to the instance and try that (maybe vagrant isn't using your VPN properly or something)
    johnypony3
    @johnypony3
    hi all, i apologize if this is answered somewhere, but i dont see it
    when i try to install this extension i get errors
    libiconv is missing. Please locate mkmf.log to investigate how it is failing.
    Bundler, the underlying system Vagrant uses to install plugins,
    reported an error. The error is shown below. These errors are usually
    caused by misconfigured plugin installations or transient network
    issues. The error from Bundler is:
    
    ERROR: Failed to build gem native extension.
    
        /opt/vagrant/embedded/bin/ruby -r ./siteconf20170920-66982-1wl8s6x.rb extconf.rb
    checking if the C compiler accepts ... yes
    checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
    Building nokogiri using packaged libraries.
    Using mini_portile version 2.3.0
    checking for iconv.h... yes
    checking for gzdopen() in -lz... yes
    checking for iconv using --with-opt-* flags... no
    checking for iconv... no
    pkg-config could not be used to find libiconv
    Please install either `pkg-config` or the pkg-config gem per
    
        gem install pkg-config -v "~> 1.1"
    
    checking for iconv using pkg-config libiconv... no
    -----
    libiconv is missing.  Please locate mkmf.log to investigate how it is failing.
    -----
    *** extconf.rb failed ***
    Could not create Makefile due to some reason, probably lack of necessary
    libraries and/or headers.  Check the mkmf.log file for more details.  You may
    need configuration options.
    
    Provided configuration options:
            --with-opt-dir
            --with-opt-include
            --without-opt-include=${opt-dir}/include
            --with-opt-lib
            --without-opt-lib=${opt-dir}/lib
            --with-make-prog
            --without-make-prog
            --srcdir=.
            --curdir
            --ruby=/opt/vagrant/embedded/bin/$(RUBY_BASE_NAME)
            --help
            --clean
            --use-system-libraries
            --enable-static
            --disable-static
            --with-zlib-dir
            --without-zlib-dir
            --with-zlib-include
            --without-zlib-include=${zlib-dir}/include
            --with-zlib-lib
            --without-zlib-lib=${zlib-dir}/lib
            --enable-cross-build
            --disable-cross-build
    
    extconf failed, exit code 1
    
    Gem files will remain installed in /Users/edward/.vagrant.d/gems/2.2.5/gems/nokogiri-1.8.1 for inspection.
    Results logged to /Users/edward/.vagrant.d/gems/2.2.5/extensions/x86_64-darwin-13/2.2.0/nokogiri-1.8.1/gem_make.out
    i ran this gem install pkg-config -v "~> 1.1" same error
    can anyone help out?
    sdeljo
    @sdeljo
    Hey Guys,
    In case you're using Slack & AWS: We built a slash(/) command tool for Slack that searches your AWS. You can find instances (by tags etc..), queues (+refresh to monitor them) and more ... If you want to play with it you can get it from here (https://www.beehive.ai/aws-on-slack). Setup is straight FW (IAM + Slack app). Would love to get feedback and ideas/or requests. Cheers,
    stiller_leser
    @stiller_leser_twitter
    Hi, can I assign a private IP any other way then setting aws.private_ip_address? The issue here is that I create a varying amount of instances in my Vagrant file and setting aws.private_ip_address would always allocate the same private ip to all machines
    Tobias Fischer
    @tfr-ffb
    @stiller_leser_twitter are you sure you set the ip in the correct scope? (like in this example: https://www.vagrantup.com/docs/multi-machine/#defining-multiple-machines )
    Alinoe Abrassart
    @alinoeabrassart
    Hello there
    I encountered an issue with sts credentials today and I was wondering if there was any interests for a pr to implement this ? I could give it some time but I'm not really used to ruby
    David Yeske
    @dyeske
    hi there, there appear to be around 500 forks of this
    David Yeske
    @dyeske
    is there a particular trick to get this to work?
    apanteleev-roox
    @apanteleev-roox
    Hi all, how I can add records about IP into /etc/hosts on two guest vm's?