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

chef/fedora-21 #333

Closed
pdostal opened this issue Mar 26, 2015 · 6 comments
Closed

chef/fedora-21 #333

pdostal opened this issue Mar 26, 2015 · 6 comments

Comments

@pdostal
Copy link

pdostal commented Mar 26, 2015

Hello all,

I hope it will be relevant to report the bug I found here:

When I created a new chef/fedora-21 virtualbox instance, the output was:

==> server11: Waiting for machine to boot. This may take a few minutes...
    server11: SSH address: 127.0.0.1:33311
    server11: SSH username: vagrant
    server11: SSH auth method: private key
    server11: Warning: Connection timeout. Retrying...
==> server11: Machine booted and ready!
==> server11: Checking for guest additions in VM...
==> server11: Setting hostname...
==> server11: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 does not seem to be present, delaying initialization.


Stderr from the command:

So I switched to chef/fedora-20 and it works properly.

My configuration is:

Vagrant.configure("2") do |config|
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.box_check_update = true
  config.vm.provider "virtualbox" do |vb|
     vb.memory = 256
  end

  (11..13).each do |i|
    config.vm.define "server#{i}" do |host|
      host.vm.box = "chef/fedora-20"
      host.vm.hostname = "server#{i}"
      host.vm.network :forwarded_port, guest: 22, host: "333#{i}", id: "ssh", auto_correct: true
      host.vm.network :private_network, ip: "192.168.245.#{i}"
      host.vm.provider "virtualbox" do |vb|
        vb.name = "server#{i}"
      end
    end
  end

end

I can use chef/fedora-20 but I think it will be nice to fix it 👍

Have a nice day !

@juliandunn
Copy link
Contributor

I believe Vagrant doesn't officially support Fedora 21 yet, therefore it doesn't know to rename the Ethernet interfaces from the driver name to ethX

hashicorp/vagrant#5277

@Tcharl
Copy link
Contributor

Tcharl commented Mar 27, 2015

No, I think it's a packaging issue.

Please look at hashicorp/vagrant#1777 (comment)

Regards,

@juliandunn
Copy link
Contributor

@Tcharl No, I don't think that's the issue, as the fedora-21 box doesn't have such a file in /etc/udev/rules.d.

@Tcharl
Copy link
Contributor

Tcharl commented Mar 28, 2015

Ok, sorry for the mistake

@rajatchopra
Copy link

Temporary fix that will change the naming scheme of interfaces:

vagrant ssh
sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
exit
vagrant package --output new_fedora21.box

^^ use the new box now. All interfaces will now be eth0,eth1.. the old way that vagrant/vbox understand.

MikaelSmith pushed a commit to MikaelSmith/puppetlabs-puppet_agent that referenced this issue Jun 8, 2015
Updates README to note Debian and Ubuntu support.
Drops Fedora 20 hosts file due to issue at
chef/bento#333
MikaelSmith pushed a commit to MikaelSmith/puppetlabs-puppet_agent that referenced this issue Jun 8, 2015
Updates README to note Debian and Ubuntu support.
Drops Fedora 20 hosts file due to issue at
chef/bento#333
MikaelSmith pushed a commit to MikaelSmith/puppetlabs-puppet_agent that referenced this issue Jun 9, 2015
Updates README to note Debian and Ubuntu support.
Drops Fedora 20 hosts file due to issue at
chef/bento#333
@cheeseplus
Copy link
Contributor

I've pushed an updated version of the box with the latest tools for each respective provider #428 and the issue no longer exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants