Issue #1 open

Vagrant fails on Windows system

kieran sheehan
created an issue

Everything is fine until i issue the 'vagrant up' command - I get the following. I have successfully installed on a mac os system.

Bringing machine 'default' up with 'virtualbox' provider... [default] Setting the name of the VM... [default] Clearing any previously set forwarded ports... [default] Creating shared folders metadata... [default] Clearing any previously set network interfaces... [default] Preparing network interfaces based on configuration... [default] Forwarding ports... [default] -- 22 => 2222 (adapter 1) [default] -- 1990 => 1990 (adapter 1) [default] -- 2990 => 2990 (adapter 1) [default] Running any VM customizations... [default] Booting VM... [default] Waiting for VM to boot. This can take a few minutes. [default] VM booted and ready for use! [default] Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!

sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces

Comments (10)

  1. Rich Manalang [Atlassian] repo owner

    Sorry, haven't had time to look into this yet. If you're blocked by this, you should just use the Atlassian SDK for now to launch an instance of JIRA or Confluence. I'll try to get to this after this week's Connect sprint which ends on Thursday.

  2. bauer_information_technology

    I got a similar error at Windows7-64:

    [default] Waiting for VM to boot. This can take a few minutes.
    [default] VM booted and ready for use!
    [default] Configuring and enabling network interfaces...
    [default] Mounting shared folders...
    [default] -- /vagrant
    [default] -- /tmp/vagrant-puppet/manifests
    [default] -- /tmp/vagrant-puppet/modules-0
    [default] Running provisioner: puppet...
    Running Puppet with default.pp...
    stdin: is not a tty
    [0;33mwarning: Could not retrieve fact fqdn[0m
    [0;36mnotice: /Stage[main]/Sudo/File[/etc/sudoers.d/]/mode: mode changed '0755'
     to '0550'[0m
    [0;36mnotice: /Stage[main]/Sudo/File[/etc/sudoers]/content: content changed '{m
    d5}683eca72967d971ee3be5cd581069b9a' to '{md5}b87ef8035e9a427e1904f12a67597b09'
    [0m
    [0;36mnotice: /Stage[main]//Exec[apt-get-update]/returns: executed successfully
    [0m
    [0;36mnotice: /Stage[main]//Package[curl]/ensure: ensure changed 'purged' to 'p
    resent'[0m
    [0;36mnotice: /Stage[main]//Package[git-core]/ensure: ensure changed 'purged' t
    o 'present'[0m
    [0;36mnotice: /Stage[main]/Java7/Apt::Ppa[ppa:webupd8team/java]/Package[python-
    software-properties]/ensure: ensure changed 'purged' to 'present'[0m
    [0;36mnotice: /Stage[main]/Java7/File[/tmp/java.preseed]/ensure: defined conten
    t as '{md5}1db94a8534ac1e1da85218161709006c'[0m
    [0;36mnotice: /Stage[main]/Java7/Apt::Ppa[ppa:webupd8team/java]/Exec[add-apt-re
    pository-ppa:webupd8team/java]/returns: executed successfully[0m
    [0;36mnotice: /Stage[main]/Apt::Update/Exec[apt_update]: Triggered 'refresh' fr
    om 1 events[0m
    [0;36mnotice: /Stage[main]/Java7/Package[oracle-java7-installer]/ensure: ensure
     changed 'purged' to 'present'[0m
    [0;36mnotice: /File[/etc/sudoers.d/README]/ensure: removed[0m
    [0;36mnotice: /Stage[main]//Sudo::Conf[vagrant]/File[10_vagrant]/ensure: create
    d[0m
    [1;35merr: /Stage[main]//Exec[install_ap3]/returns: change from notrun to 0 fai
    led: sudo su -c 'curl https://bitbucket.org/atlassian/ap3-sdk-bin/raw/master/ap3
    -setup.sh | sh' vagrant returned 1 instead of one of [0] at /tmp/vagrant-puppet/
    manifests/default.pp:38[0m
    [0;36mnotice: /Stage[main]//Exec[start_jira_in_background]: Dependency Exec[ins
    tall_ap3] has failures: true[0m
    [0;33mwarning: /Stage[main]//Exec[start_jira_in_background]: Skipping because o
    f failed dependencies[0m
    [0;36mnotice: /Stage[main]//Notify[done]: Dependency Exec[install_ap3] has fail
    ures: true[0m
    [0;33mwarning: /Stage[main]//Notify[done]: Skipping because of failed dependenc
    ies[0m
    [0;36mnotice: Finished catalog run in 84.70 seconds[0m
    The following SSH command responded with a non-zero exit status.
    Vagrant assumes that this means the command failed!
    
    puppet apply --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' --
    detailed-exitcodes /tmp/vagrant-puppet/manifests/default.pp || [ $? -eq 2 ]
    
    C:\development\atlassian-connect-jira-vagrant>
    
  3. Log in to comment